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 :)
They could if only I had any time. Alas, there's so much work elsewhere in
the kernel. :-)
> 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
I'm seeing even three of them now! :-)
Perhaps, branching should be considered? :-)
> to fix some of these issues happily reviewed :)
Erm, it's either you created the trees too soon, or we (most probably)
dalayed with updating the patches too much. The thing is, I have reworked TX49
driver and also renamed it following the recent, suffixing scheme -- I know
git can handle renames but patch(1) cannot. How should we handle this?
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
