From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Thomas Koeller <thomas.koeller@baslerweb.com>
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>
Subject: Re: [PATCH] RM9000 serial driver
Date: Wed, 30 Aug 2006 15:59:57 +0400 [thread overview]
Message-ID: <44F57DBD.9020700@ru.mvista.com> (raw)
In-Reply-To: <200608300105.26921.thomas.koeller@baslerweb.com>
Hello.
Thomas Koeller 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?
The iotype is passed to driver when registering the platform device or
calling early_serial_setup().
There's absolutely no way for 8250.c to figure it out yourself. Please, review
the driver's code more carefully. It was not at all that complex task to copy
from the existing Alchemy code...
> Thomas
WBR, Sergei
next prev parent reply other threads:[~2006-08-30 11:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 21:18 [PATCH] RM9000 serial driver Thomas Koeller
2006-08-11 19:39 ` Sergei Shtylyov
2006-08-15 21:15 ` Thomas Koeller
2006-08-15 21:35 ` Sergei Shtylyov
2006-08-21 22:57 ` Thomas Koeller
2006-08-22 0:59 ` Yoichi Yuasa
2006-08-22 20:27 ` Thomas Koeller
2006-08-29 15:14 ` Sergei Shtylyov
2006-08-29 23:05 ` Thomas Koeller
2006-08-30 11:59 ` Sergei Shtylyov [this message]
2006-08-25 22:38 ` Thomas Koeller
2006-08-26 3:56 ` Jonathan Day
2006-08-29 13:32 ` Sergei Shtylyov
2006-08-29 19:04 ` Russell King
2006-08-29 19:37 ` Sergei Shtylyov
2006-08-29 19:59 ` Russell King
2006-08-30 21:16 ` Thomas Koeller
2006-08-29 23:00 ` Thomas Koeller
2006-08-30 12:12 ` Russell King
2006-08-30 16:50 ` Sergei Shtylyov
2007-02-10 16:11 ` Thomas Koeller
2007-02-10 18:20 ` Sergei Shtylyov
2007-02-12 0:28 ` Thomas Koeller
2007-02-12 0:57 ` Thomas Koeller
2006-08-30 21:28 ` Thomas Koeller
2006-08-31 7:24 ` Sergei Shtylyov
2006-08-30 13:22 ` Sergei Shtylyov
2006-08-30 14:18 ` Sergei Shtylyov
2006-08-30 16:23 ` Sergei Shtylyov
2006-09-09 17:19 ` Sergei Shtylyov
2006-08-30 12:15 ` Russell King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44F57DBD.9020700@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=rmk+serial@arm.linux.org.uk \
--cc=thomas.koeller@baslerweb.com \
--cc=thomas@koeller.dyndns.org \
--cc=yoichi_yuasa@tripeaks.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.