From: Russell King <rmk@arm.linux.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: DevilKin <devilkin-lkml@blindguardian.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.50 - 8250_cs does NOT work
Date: Mon, 7 Oct 2002 09:40:26 +0100 [thread overview]
Message-ID: <20021007094026.B803@flint.arm.linux.org.uk> (raw)
In-Reply-To: <18990.1033979667@passion.cambridge.redhat.com>; from dwmw2@infradead.org on Mon, Oct 07, 2002 at 09:34:27AM +0100
On Mon, Oct 07, 2002 at 09:34:27AM +0100, David Woodhouse wrote:
> Doesn't compile. ALPHA_KLUDGE_MCR undefined. That crap in the generic 8250
> code should go away in favour of some mask bits set by the platform-specific
> code when it registers the ports. You probably want to set the default _and_
> the permitted bits that way.
Oddly, thats what DevilKin reported. This isn't the patch I sent Linus.
8)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
prev parent reply other threads:[~2002-10-07 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 10:57 2.4.50 - 8250_cs does NOT work DevilKin
2002-10-02 11:05 ` Russell King
2002-10-02 11:48 ` DevilKin
2002-10-02 12:23 ` DevilKin
2002-10-07 8:34 ` David Woodhouse
2002-10-07 8:40 ` Russell King [this message]
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=20021007094026.B803@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=devilkin-lkml@blindguardian.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox