public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Russell King <rmk@arm.linux.org.uk>
Subject: Re: [PATCH] 8250: Let arch provide the list of leagacy ports	dynamically
Date: Sat, 23 Oct 2004 11:51:35 +1000	[thread overview]
Message-ID: <1098496295.6008.129.camel@gaston> (raw)
In-Reply-To: <E1CLAvB-00041B-00@gondolin.me.apana.org.au>

On Sat, 2004-10-23 at 11:42, Herbert Xu wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> > 
> > a #define of an array. This finally allows to fix the problem of
> > platforms like ppc and ppc64 for which the same kernel can boot
> > machines with and without a 8250, and is necessary to properly deal
> 
> That sounds great because we're seeing the same problem with i8042
> on ppc/ppc64.  Do you have any plans for that driver?

There is a different patch "[PATCH] ppc64: Add mecanism to check existence
of legacy ISA devices" that I posted today that does that for ppc64,
however, Linus seem to prefer something different involving porting
the pnp core to ppc64 and adapting those drivers to rely on it, which
I don't have time to do at the moment.

Ben.



      reply	other threads:[~2004-10-23  1:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 23:37 [PATCH] 8250: Let arch provide the list of leagacy ports dynamically Benjamin Herrenschmidt
2004-10-23  1:42 ` Herbert Xu
2004-10-23  1:51   ` Benjamin Herrenschmidt [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=1098496295.6008.129.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@osdl.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