From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: IDE - sensible probing for PCI systems
Date: Mon, 27 Jun 2005 17:24:39 +0100 [thread overview]
Message-ID: <20050627172439.C17140@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.61L.0506271519060.23903@blysk.ds.pg.gda.pl>; from macro@linux-mips.org on Mon, Jun 27, 2005 at 03:55:39PM +0100
On Mon, Jun 27, 2005 at 03:55:39PM +0100, Maciej W. Rozycki wrote:
> On Sat, 25 Jun 2005, Alan Cox wrote:
>
> > PC systems have serial at 0x3f8/0x2f8 (lpc bus), almost always PS/2 port
>
> Strange -- boxes have started to appear that have no connectors or at
> least PCB headers for them. What's the point in removing connectors and
> leaving the (otherwise useful) hardware inaccessible?
It's far easier for a mobo manufacturer to remove the connectors and
PCB tracking for the connections. For all we know, PCI southbridges
with serial ports integrated into them may still be cheaper in quantity
than ones without - so if mobo manufacturers want to get rid of the
serial ports their easiest way is to omit the connectors and associated
PCB tracks.
> > > That is what surprises me and what my whole consideration is about.
> > > It's just I don't see a need for such a setup anymore and for a system
> > > with no ISA or EISA bridge I'd expect all that legacy to be gone leaving
> > > us with no need to handle implicit resources. But has any manufacturer
> > > produced such an i386 system yet?
> >
> > Whats the _economic_ incentive to do so ? There basically isnt one.
>
> One chip less? Well, perhaps the cost of R&D for such a system would
> exceed the total cost of keeping that chip included in all boards
> manufactured during the term corporate planning is able to cover....
The southbridge typically contains the other things like the RTC, etc.
What you're suggesting isn't just a case of "removing a chip" - it's
more a case of designing a replacement without a lot of the legacy
stuff in.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-06-27 16:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 12:23 Alan Cox
2005-06-21 13:42 ` Maciej W. Rozycki
2005-06-21 14:12 ` Alan Cox
2005-06-21 15:10 ` Maciej W. Rozycki
2005-06-21 18:46 ` Alan Cox
2005-06-23 18:22 ` Maciej W. Rozycki
2005-06-23 22:48 ` Alan Cox
2005-06-24 11:52 ` Maciej W. Rozycki
2005-06-24 22:41 ` Jeff Garzik
2005-06-27 14:18 ` Maciej W. Rozycki
2005-06-27 20:31 ` Bill Davidsen
2005-06-25 12:32 ` Alan Cox
2005-06-27 14:55 ` Maciej W. Rozycki
2005-06-27 16:24 ` Russell King [this message]
2005-06-27 19:54 ` Alan Cox
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=20050627172439.C17140@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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
Powered by JetHome