public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: rename generic_defconfig to defconfig?
Date: Wed, 22 Sep 2004 23:02:08 +0000	[thread overview]
Message-ID: <200409221702.08764.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200409221713.12673.jbarnes@engr.sgi.com>

On Wednesday 22 September 2004 3:13 pm, Jesse Barnes wrote:
> Just thought I'd float the idea of making the ia64 defconfig into a generic 
> ia64 kernel config.  It's probably easiest just to rename generic_defconfig 
> to defconfig since that already works everywhere (well, except for akpm's box 
> apparently).  That would make it extra easy to build a working kernel for the 
> various ia64 boxes out there...

Sounds like a good idea to me.  If the idea is to make it as easy as
possible to build working kernels, maybe we should also make some
things static rather than modules.  For starters:

 CONFIG_TULIP (HP superdome core I/O and 4-port cards)
 CONFIG_E100  (i2000)
 CONFIG_E1000 (Tiger)
 CONFIG_USB_EHCI_HCD (HP boxes)
 CONFIG_USB_OHCI_HCD (HP boxes)
 CONFIG_USB_HID

Or maybe I'm the only one who's too lazy to mess with modules
for every build.

I think generic_defconfig currently builds a McKinley kernel,
which may be the right thing, but you do have to remember
to switch back to CONFIG_ITANIUM for i2000.

  parent reply	other threads:[~2004-09-22 23:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 21:13 rename generic_defconfig to defconfig? Jesse Barnes
2004-09-22 21:25 ` Luck, Tony
2004-09-22 21:28 ` Matthew Wilcox
2004-09-22 21:29 ` Jesse Barnes
2004-09-22 23:02 ` Bjorn Helgaas [this message]
2004-09-22 23:05 ` Peter Chubb
2004-09-22 23:05 ` Luck, Tony
2004-09-22 23:21 ` Jesse Barnes
2004-09-22 23:23 ` Jesse Barnes
2004-09-22 23:25 ` Luck, Tony
2004-11-01 22:34 ` Jesse Barnes
2004-11-02 18:35 ` Luck, Tony
2004-11-02 19:36 ` Jesse Barnes
2004-11-02 21:51 ` Luck, Tony

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=200409221702.08764.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=linux-ia64@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