From: "David S. Miller" <davem@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: [SPARC32] Early kernel panic with 2.6.1rc1
Date: Mon, 05 Jan 2004 09:17:45 +0000 [thread overview]
Message-ID: <20040105011745.3a6603e2.davem@redhat.com> (raw)
In-Reply-To: <1073231988.22653.23.camel@zorak>
On Mon, 5 Jan 2004 03:05:58 -0500 (EST)
Ricky Beam <jfbeam@bluetronic.net> wrote:
> On Sun, 4 Jan 2004, David S. Miller wrote:
> >We cannot just depend upon PCI however for the 8250 driver options
> >as it may appear also in ISA and onboard forms.
>
> No sparc32 or sparc64 system (that I know of) contain an actual 8250.
> Furthermore, the only systems to have an ISA bus are PCI systems (PCI-ISA
> bridged.) Granted, I've not used an SBUS based system in several years.
The 8250 drives all variants, including the kind used for the 'su' devices
in PCI sparc64 systems, this is what Peter was talking about when he alluded
to merging the sunsu.c driver into the 8250.c code.
Also, any system that has a PCI bus can therefore host one of those
serial/parallel PCI cards which use 8250 chips often.
So I stand where I started, that adding conditions to the 8250 Kconfig
option is totally pointless as no selection of checks are totally suitable.
next prev parent reply other threads:[~2004-01-05 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 15:59 [SPARC32] Early kernel panic with 2.6.1rc1 Tom 'spot' Callaway
2004-01-04 16:54 ` Tom 'spot' Callaway
2004-01-04 22:19 ` Keith M Wesolowski
2004-01-04 22:38 ` Tom 'spot' Callaway
2004-01-04 22:48 ` Keith M Wesolowski
2004-01-04 23:15 ` Tom 'spot' Callaway
2004-01-05 0:28 ` David S. Miller
2004-01-05 4:17 ` Pete Zaitcev
2004-01-05 8:05 ` Ricky Beam
2004-01-05 9:17 ` David S. Miller [this message]
2004-01-05 21:26 ` Tom 'spot' Callaway
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=20040105011745.3a6603e2.davem@redhat.com \
--to=davem@redhat.com \
--cc=sparclinux@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 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.