mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jcwren@jcwren.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Machin dependent serial port patches
Date: Wed, 28 May 2003 10:44:09 +0100	[thread overview]
Message-ID: <1054115049.2082.142.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <1053432549.30546.5.camel@dhcp22.swansea.linux.org.uk>

On Tue, 2003-05-20 at 13:09, Alan Cox wrote:
> On Maw, 2003-05-20 at 01:56, J.C. Wren wrote:
> > 	One of the things I noticed in the port of 2.5.69 to the 386EX embedded 
> > system is that serial.h appears to not be a mach-xxx positionable file.  The 
> > 386EX board uses standard 8250 type serial ports, but at 3.6864Mhz instad of 
> > 1.8432Mhz.  There appears to be no way to build a patch set without modifying 
> > include/i386/serial.h.  Would this not be better places in mach-defaults?  
> > I'm trying very hard to modify as few files as possible when building these 
> > patch sets.
> 
> Making asm-i386/serial.h include a mach- file sounds the right thing to
> do. mach- for x86 is pretty new so a lot of stuff that maybe should be
> in it, hasnt migrated yet.

I disagree. I think it would be better to get rid of the hard-coded
table altogether and let something in the machine-specific code call
register_serial() during early boot.

Even on PeeCee hardware, that lets us do the superio chip probe and
potentially register high-speed serial ports, before the pnpbios probe
and finally falling back to the old standard I/O addresses.

-- 
dwmw2


      parent reply	other threads:[~2003-05-28  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20  0:56 J.C. Wren
2003-05-20 12:09 ` Alan Cox
2003-05-20 13:57   ` J.C. Wren
2003-05-28  9:44   ` David Woodhouse [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=1054115049.2082.142.camel@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jcwren@jcwren.com \
    --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

all inboxes | Powered by JetHome®