From: Ralf Baechle <ralf@linux-mips.org>
To: Daniel Jacobowitz <dan@debian.org>
Cc: linux-mips@linux-mips.org
Subject: Re: ddb5477 fixes for 2.6
Date: Sun, 21 Sep 2003 02:21:48 -0700 [thread overview]
Message-ID: <20030921092148.GD1578@linux-mips.org> (raw)
In-Reply-To: <20030918163344.GA22013@nevyn.them.org>
On Thu, Sep 18, 2003 at 12:33:44PM -0400, Daniel Jacobowitz wrote:
> Here's just enough to make the ddb5477 compile and boot. The defconfig has
> lost the onboard network card, and you also need to turn on CONFIG_EMBEDDED
> to turn off CONFIG_VT. Otherwise, conswitchp is uninitialized, causing a
> crash. If I initialize it to &dummy_con, serial consoles stop working
> (???).
I'm not exactly happy about the way various unrelated options are lumped
together behind CONFIG_EMBEDDED; it seems worse than the problem it's
meant to solve ...
> Userspace doesn't work - lots of scripts segfault, portmap times out, there
> are a number of other glitches. init=/bin/bash hangs. But at least it's
> progress.
>
> I update CFLAGS for gcc 3.3/binutils 2.14. I think asking people to use
> vaguely modern tools for 2.6 is reasonable. And the old flags don't work
> any more. This should work with 3.2 too.
As long as current gcc stays as slow as it is I'm going to stick to
something old. And I'm not alone.
> The PCI and ac97 changes are pretty mindless merge work.
>
> Ralf, this re-adds CONFIG_PCI_AUTO. Do you know where it went? :) Probably
> a lot of other boards are sad about its disappearance also.
CONFIG_PCI_AUTO went the way to /dev/zero; it not only made the PCI
maintainers make funny sounds it simply seemed superfluous - the PCI
code is supposed to be able to fully configure a PCI bus itself if only
it's used properly.
Ralf
prev parent reply other threads:[~2003-09-22 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 16:33 ddb5477 fixes for 2.6 Daniel Jacobowitz
2003-09-18 17:04 ` Maciej W. Rozycki
2003-09-18 17:06 ` Daniel Jacobowitz
2003-09-18 17:19 ` Maciej W. Rozycki
2003-09-18 17:22 ` Daniel Jacobowitz
2003-09-21 9:21 ` Ralf Baechle [this message]
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=20030921092148.GD1578@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=dan@debian.org \
--cc=linux-mips@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