Date: Sat, 13 May 2006 23:41:16 +0000 (UTC) From: Olivier Houchard <cognet@FreeBSD.org> To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/conf options.arm src/sys/arm/conf SKYEYE src/sys/arm/include pmap.h src/sys/arm/at91 at91.c at91_st.c if_ate.c uart_bus_at91usart.c uart_cpu_at91rm9200usart.c uart_dev_at91usart.c Message-ID: <200605132341.k4DNfGGl067134@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
cognet 2006-05-13 23:41:16 UTC
FreeBSD src repository
Modified files:
sys/conf options.arm
sys/arm/conf SKYEYE
sys/arm/include pmap.h
sys/arm/at91 at91.c at91_st.c if_ate.c
uart_bus_at91usart.c
uart_cpu_at91rm9200usart.c
uart_dev_at91usart.c
Log:
Resurrect Skyeye support :
Add a new option, SKYEYE_WORKAROUNDS, which as the name suggests adds
workarounds for things skyeye doesn't simulate. Specifically :
- Use USART0 instead of DBGU as the console, make it not use DMA, and manually provoke an interrupt when we're done in the transmit function.
- Skyeye maintains an internal counter for clock, but apparently there's
no way to access it, so hack the timecounter code to return a value which
is increased at every clock interrupts. This is gross, but I didn't find a
better way to implement timecounters without hacking Skyeye to get the
counter value.
- Force the write-back of PTEs once we're done writing them, even if they
are supposed to be write-through. I don't know why I have to do that.
Revision Changes Path
1.6 +8 -0 src/sys/arm/at91/at91.c
1.3 +17 -1 src/sys/arm/at91/at91_st.c
1.7 +1 -1 src/sys/arm/at91/if_ate.c
1.3 +5 -7 src/sys/arm/at91/uart_bus_at91usart.c
1.2 +3 -7 src/sys/arm/at91/uart_cpu_at91rm9200usart.c
1.6 +12 -12 src/sys/arm/at91/uart_dev_at91usart.c
1.3 +2 -1 src/sys/arm/conf/SKYEYE
1.17 +5 -0 src/sys/arm/include/pmap.h
1.8 +2 -1 src/sys/conf/options.arm
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605132341.k4DNfGGl067134>