All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: sparclinux@vger.kernel.org
Subject: Re: klibc and SPARC
Date: Wed, 17 May 2006 22:36:21 +0000	[thread overview]
Message-ID: <446BA565.7070608@zytor.com> (raw)
In-Reply-To: <e4g1ho$dae$1@terminus.zytor.com>

David S. Miller wrote:
>> Does it make sense to say that these prom configurations are only
>> recognized by kinit if openpromfs is available (without which it will
>> simply behave as on any other platform), or should I go through the
>> additional trouble of supporting both methods?
> 
> You need to enable a particular driver either way,
> either CONFIG_SUN_OPENPROMFS or CONFIG_SUN_OPENPROMIO.
> 
> The NFS configuration bits you are moving into klibc
> are going to be expected to work even if both of those
> config options are disabled, it's expected to always
> be available and work.

Sounds like you're saying I should force one of those drivers enabled, is that right?  I'm 
fine with that.  The other alternative is of course to put an ad hoc thing for this thing; 
that seems unnecessarily ugly to me but if necessary I can do that as well.

If I should force one of the drivers enabled, which one should it be (I'm assuming 
CONFIG_SUN_OPENPROMFS?)

	-hpa


  parent reply	other threads:[~2006-05-17 22:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 20:37 klibc and SPARC H. Peter Anvin
2006-05-17 20:40 ` David S. Miller
2006-05-17 20:43 ` H. Peter Anvin
2006-05-17 20:57 ` H. Peter Anvin
2006-05-17 22:32 ` David S. Miller
2006-05-17 22:36 ` H. Peter Anvin [this message]
2006-05-17 22:41 ` David S. Miller
2006-05-17 23:10 ` H. Peter Anvin
2006-05-17 23:33 ` David S. Miller
2006-05-17 23:38 ` H. Peter Anvin
2006-05-18 19:17 ` H. Peter Anvin
2006-05-18 19:46 ` David S. Miller
2006-05-18 20:16 ` H. Peter Anvin

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=446BA565.7070608@zytor.com \
    --to=hpa@zytor.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.