On Mon, Sep 04, 2006 at 09:59:17PM +0400, Sergei Shtylyov wrote: > Hello. > > Tom Rini wrote: > > >> Erm, I have a separate KGDB driver for Alchemy UART form the time when > >> it was still driven by its own driver, au1x00_uart.c, not by 8250.c. > >> The issue with it was that even if port unregistering call is added it > >>wouldn't work because a buglet in uart_match_port() wouldn't allow > >>unregistering. I have now sent the trivial fix for that buglet to Russel > >>and he's accepted it. The question is: do we need the Alchemy code > >>integrated to 8250_kgdb.c (that being somewhat non-trivial addition) or > >>can it still live in its own driver? > > >Well, can you do it cleanly? > > Hm, having just remembered how tricky Alchemy UARTs are WRT the UART > number to line number correspondence -- the number of UARTs varies from 2 > to 4 depending on SOC, they're not numbered in sequence (like Au1500 having > UARTs #0 and #3), and some of them may also be disabled by a bootloader, > the answer is "that would be non-trivial". :-)
Non-trivial and clean can co-exist :) Anyhow, there are definitely a few issues with the serial code right now. I've put up git/stacked git trees of what's current now. Patches to fix some of these issues happily reviewed :) Otherwise it might have to wait a bit as right now I'm trying to see what's wrong with i386 support. I had it working at some point this morning, but then all of the sudden it broke (bad interaction with the new CFI stuff? I don't know). -- Tom Rini ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
