|To:||Marc St-Jean <Marc_St-Jean@pmc-sierra.com>|
|Subject:||Re: [PATCH] serial driver PMC MSP71xx, kernel linux-mips.git mast er|
|From:||Sergei Shtylyov <email@example.com>|
|Date:||Thu, 25 Jan 2007 17:29:25 +0300|
|Cc:||Alan <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com|
|Organization:||MontaVista Software Inc.|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; rv:1.7.2) Gecko/20040803|
Hello. Marc St-Jean wrote:
> I could use both iotype and type with a test on each for the appropriate > bug, what do you recommend?
I think iotype would be enough. You can't pass type for platform devices anyway, IIRC (the thing I don't quite like).
I just found that out the hard way, it get's overwritten during autoconfig* and ends up back at PORT_16550A.
I'm now trying to use my own iotype = UPIO_DWAPB and I've added it to all cases that check for UPIO_MEM. However at boot time I'm getting: "serial8250: ttyS0 at *unknown* (irq = 27) is a 16550A". It looks like something outside of 8250.c must be checking for UPIO_MEM, I'm looking into it.
Yeah, be sure to change serial_core.c as well (whereever you'll see UPIO_AU/TSI there)... Quite ugly. :-/
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH] MMC: au1xmmc R6 response support, Pierre Ossman|
|Next by Date:||Re: [PATCH] serial driver PMC MSP71xx, kernel linux-mips.git master, Sergei Shtylyov|
|Previous by Thread:||Re: [PATCH] serial driver PMC MSP71xx, kernel linux-mips.git mast er, Marc St-Jean|
|Next by Thread:||Re: [PATCH] serial driver PMC MSP71xx, kernel linux-mips.git mast er, Marc St-Jean|
|Indexes:||[Date] [Thread] [Top] [All Lists]|