All of lore.kernel.org
 help / color / mirror / Atom feed
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 00:28:31 +0000	[thread overview]
Message-ID: <20040104162831.40901ef6.davem@redhat.com> (raw)
In-Reply-To: <1073231988.22653.23.camel@zorak>

On Sun, 04 Jan 2004 17:15:58 -0600
"Tom 'spot' Callaway" <tcallawa@redhat.com> wrote:

> On Sun, 2004-01-04 at 16:48, Keith M Wesolowski wrote:
> 
> > This really isn't the right thing to depend on, although I'm not sure
> > what is.  This chip is found almost everywhere.
> 
> Is it natively found in any model of 32bit SPARC? The only possible way
> I can think of getting one in a sparc32 machine is by adding a PCI 8250
> card to a JavaStation, which the PROM won't recognize anyway.

I think we should not disallow this option, as the device may very
well appear on PCI systems.

We cannot just depend upon PCI however for the 8250 driver options
as it may appear also in ISA and onboard forms.

I do not see any reason why allowing this option to be enabled is a problem.
People just have to become knowledgable about what kind of hardware
they actually have right? :)

  parent reply	other threads:[~2004-01-05  0:28 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 [this message]
2004-01-05  4:17 ` Pete Zaitcev
2004-01-05  8:05 ` Ricky Beam
2004-01-05  9:17 ` David S. Miller
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=20040104162831.40901ef6.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.