From: Jurij Smakov <jurij@wooyd.org>
To: sparclinux@vger.kernel.org
Subject: Re: [2.6.19.1] ESP regression ?
Date: Sat, 06 Jan 2007 05:22:13 +0000 [thread overview]
Message-ID: <20070106052213.GA4880@droopy.oc.cox.net> (raw)
In-Reply-To: <459E1EC7.7050300@systella.fr>
On Fri, Jan 05, 2007 at 01:35:05PM -0600, Tom 'spot' Callaway wrote:
>
> Building the SCSI and esp components into the kernel does not change the
> results, it still doesn't work on 2.6.18.1+ on sparc32.
>
> If anyone has a working sparc32 kernel config that works on a sparc32
> w/esp, please post it here.
Tom,
The 2.6.18 kernel (it is actually 2.6.18.5 plus some patches) we
currently have in Debian works fine on my SS20. You can find the
config, kernel, and matching initrd at
http://www.wooyd.org/sparc/
The only patch which touches anything in arch/sparc is also included
there (bus-id-size.patch), other patches may be viewed at
http://svn.debian.org/wsvn/kernel/dists/sid/linux-2.6/debian/patches/
One esp problem I'm aware of is broken CD-ROM support, the bug report
with some discussion is available at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug93894
I've got as far as figuring out that this problem seems to be due to a
miscompilation with gcc 4.1. If the kernel is built with gcc 4.0,
CD-ROM actually works again, so it might be some tool chain
regression. At this point, however, I don't really have time to track
it down.
Best regards,
--
Jurij Smakov jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
next prev parent reply other threads:[~2007-01-06 5:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 9:47 [2.6.19.1] ESP regression ? BERTRAND Joël
2007-01-05 17:45 ` Tom 'spot' Callaway
2007-01-05 19:35 ` Tom 'spot' Callaway
2007-01-06 5:22 ` Jurij Smakov [this message]
2007-01-06 9:09 ` BERTRAND Joël
2007-01-07 14:23 ` BERTRAND Joël
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=20070106052213.GA4880@droopy.oc.cox.net \
--to=jurij@wooyd.org \
--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.