From: Paul Laufer <paul@laufernet.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Andrew Morton <akpm@digeo.com>,
niteowl@intrinsity.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5.59 kernel bugs
Date: Fri, 28 Feb 2003 01:14:21 -0800 [thread overview]
Message-ID: <20030228091421.GA617@hal9000.laufernet.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0302061504330.10714-100000@dragon.pdx.osdl.net>
SOUND_SB is fixed as of 2.5.62 or so. Work is being done on
SOUND_AWE32_SYNTH but the structure of the driver doesn't fit the new
PnP API and is going to require quite a bit of rewrite. Not sure how
many people still use these old ISA sound cards... I only had a
handful of volunteers this time around to help test the soundblaster
fixes. During 2.3 there was significantly more interest for this once
wildly popular sound card. Other drivers for cards like the PAS16 that
weren't popular to begin with (and are 10+ years old) may have trouble
finding someone willing to update it.
Paul
On Thu, Feb 06, 2003 at 03:06:31PM -0800 or thereabouts, Randy.Dunlap wrote:
> On Thu, 6 Feb 2003, Dave Jones wrote:
[Snip]
> I did a 'make allyesconfig' build about 10 days ago. I kept a list of
> modules that I had to disable due to syntax errors and another list of
> linker errors. Here's that list, for 2.5.59:
>
>
> make some things build during allyesconfig testing:
> syntax errors:
[snip long list]
> ###
> make -f scripts/Makefile.build obj=arch/i386/boot arch/i386/boot/bzImage
> make -f scripts/Makefile.build obj=arch/i386/boot/compressed \
> IMAGE_OFFSET=0x100000 arch/i386/boot/compressed/vmlinux
> arch/i386/boot/tools/build -b arch/i386/boot/bootsect arch/i386/boot/setup arch/i386/boot/vmlinux.bin CURRENT > arch/i386/boot/bzImage
> Root device is (3, 4)
> Boot sector 512 bytes.
> Setup is 4880 bytes.
> System is 8384 kB
> System is too big. Try using modules.
> make[1]: *** [arch/i386/boot/bzImage] Error 1
> make: *** [bzImage] Error 2
>
>
> --
> ~Randy
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-02-28 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 20:43 2.5.59 kernel bugs niteowl
2003-02-06 21:08 ` Martin J. Bligh
2003-02-06 23:16 ` Alan Cox
2003-02-06 22:33 ` Martin J. Bligh
2003-02-06 21:16 ` Andrew Morton
2003-02-06 22:49 ` Dave Jones
2003-02-06 23:06 ` Randy.Dunlap
2003-02-28 9:14 ` Paul Laufer [this message]
2003-02-07 0:14 ` Russell King
2003-02-07 9:23 ` Oleg Drokin
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=20030228091421.GA617@hal9000.laufernet.com \
--to=paul@laufernet.com \
--cc=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=niteowl@intrinsity.com \
--cc=rddunlap@osdl.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