| To: | Sergei Shtylyov <sshtylyov@ru.mvista.com> |
|---|---|
| Subject: | Re: [PATCH] RM9000 serial driver |
| From: | Thomas Koeller <thomas.koeller@baslerweb.com> |
| Date: | Wed, 30 Aug 2006 01:05:26 +0200 |
| Cc: | Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>, rmk+serial@arm.linux.org.uk, linux-serial@vger.kernel.org, ralf@linux-mips.org, linux-mips@linux-mips.org, Thomas Köller <thomas@koeller.dyndns.org> |
| In-reply-to: | <44F459DD.8060902@ru.mvista.com> |
| Organization: | Basler AG |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <200608102318.52143.thomas.koeller@baslerweb.com> <200608222227.20181.thomas.koeller@baslerweb.com> <44F459DD.8060902@ru.mvista.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | KMail/1.9.3 |
On Tuesday 29 August 2006 17:14, Sergei Shtylyov wrote: > > Also, it seems to me that the whole register-mapping stuff conflicts with > > autodetection, because autoconfig() uses serial_inp() and serial_outp() > > before the port types, and hence the mapping requirements, are known. > > Port types have nothing to do with this. Or at least they hadn't until > your recent patch. :-) > iotype was used to identify the addressing scheme, and it's alsready > known beforehand. How so? If I do not yet know which hardware I am dealing with, how can I know the iotype? Thomas -- Thomas Koeller, Software Development Basler Vision Technologies An der Strusbek 60-62 22926 Ahrensburg Germany Tel +49 (4102) 463-390 Fax +49 (4102) 463-46390 mailto:thomas.koeller@baslerweb.com http://www.baslerweb.com |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] RM9000 serial driver, Russell King |
|---|---|
| Next by Date: | Re: [PATCH] RM9000 serial driver, Thomas Koeller |
| Previous by Thread: | Re: [PATCH] RM9000 serial driver, Sergei Shtylyov |
| Next by Thread: | Re: [PATCH] RM9000 serial driver, Sergei Shtylyov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |