From: Randolph Chung <tausq@debian.org>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] sym53c8xx.c
Date: Wed, 14 May 2003 15:25:47 -0700 [thread overview]
Message-ID: <20030514222547.GT548@tausq.org> (raw)
In-Reply-To: <20030514215849.GK6859@parcelfarce.linux.theplanet.co.uk>
> The sym53c8xx driver is near to being removed from 2.6. Can anyone think
> of a situation where we might still want it? I'm concerned that maybe
> some of the fixes didn't go into the sym53c8xx_2 driver. In particular,
> I'd like to know that the sym53c8xx_2 driver in 2.5 works on C3k (wide &
> narrow!) and A500.
it definitely works on a500 with 2.5, and on c3k (narrow & wide) with
2.4. I am still not able to boot up my c3k with 2.5 because of the
suckyio serial console problems :(
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2003-05-14 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 21:58 [parisc-linux] sym53c8xx.c Matthew Wilcox
2003-05-14 22:19 ` James Bottomley
2003-05-14 22:25 ` Randolph Chung [this message]
2003-05-15 10:20 ` Thibaut VARÈNE
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=20030514222547.GT548@tausq.org \
--to=tausq@debian.org \
--cc=parisc-linux@parisc-linux.org \
--cc=willy@debian.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