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". :-)
The current driver doesn't allow port selection via 'make config' and uses
UART3 (or UART1 on Au1200) based on the #define somewhere in the Alchemy
headers.
That would be non trivial not only for that reason of course: Alchemy
UARTs are 16550A-workalikes but not compatible to it -- the registers are
mapped differently because the chip designers didn't want to copy quite
perverted addressing scheme of 16550 I guess...
> What are we going to gain by putting it in 8250_kgdb.c ?
Async breakpoint for Alchemy. :-)
> That's what we need to answer first.
Well, actually adding the proper unregistering code to the exisiting
driver would be easiest thing to do. This way, we have a chance of submitting
it into the -mm tree now...
WBR, Sergei
-------------------------------------------------------------------------
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
