Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] ncr53c8xx patch for c110
Date: 21 Jun 2004 11:17:04 -0500	[thread overview]
Message-ID: <1087834626.1797.38.camel@mulgrave> (raw)
In-Reply-To: <40BD9F870000CE2A@ocpmta2.freegates.net>

On Mon, 2004-06-21 at 11:11, Joel Soete wrote:
> It should be. The c110 also have such LASI ASIC chip ;) and on its scsi
> port I connected a CRW drive. This week-end I tried to uncompress-untar
> the src of my working kernel tree burned on a cd. but the operation failled
> with an i/o error.
> At this moment, I didn't check more (too much focused on the ncr 720 patch)
> but I just check on my hpux b180 and there  is any pb to read the cd. So
> either the drive is realy broken (but I already reach to burn and scan a
> full 600Mb cd-rwwith a previous kernel) or there is a pb with 53c7[01]0
> driver too?
> 
> James can you give us your opinion about this ?

I know of no outstanding problems with the 53c700 driver in the 2.6
kernel (and I use it all the time, since my other voyager has a D700
53c700-66 device for its root discs).

James


_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2004-06-21 16:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 16:11 [parisc-linux] ncr53c8xx patch for c110 Joel Soete
2004-06-21 16:17 ` James Bottomley [this message]
     [not found] <40BD9F8700009BB8@ocpmta2.freegates.net>
     [not found] ` <1087569206.2078.13.camel@mulgrave>
     [not found]   ` <40D30E3C.1010809@tiscali.be>
2004-06-18 20:01     ` Joel Soete
2004-06-20  5:55       ` Andy Walker
2004-06-21  7:48       ` Andy Walker

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=1087834626.1797.38.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=parisc-linux@parisc-linux.org \
    --cc=soete.joel@tiscali.be \
    /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