All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Peter Rival <frival@zk3.dec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug in 2.5.1
Date: Tue, 18 Dec 2001 17:44:45 +0100	[thread overview]
Message-ID: <20011218174445.H32511@suse.de> (raw)
In-Reply-To: <8A43C34093B3D5119F7D0004AC56F4BCC3441C@difpst1a.dif.dk> <3C1F305C.9030702@t-online.de> <3C1F5311.2070407@t-online.de> <20011218155357.G32511@suse.de> <3C1F6E8D.6070704@zk3.dec.com>
In-Reply-To: <3C1F6E8D.6070704@zk3.dec.com>

On Tue, Dec 18 2001, Peter Rival wrote:
> Jens Axboe wrote:
> 
> >On Tue, Dec 18 2001, Hans-Otto Ahl wrote:
> >
> >>Hans-Otto Ahl wrote:
> >>
> >>
> >>>Jesper Juhl wrote:
> >>>
> >>>
> >>>>> Hi chaps, sorry to inform you about a problem in 'ide-floppy' drivers
> >>>>> and in the module as well.
> >>>>
> >
> >Apply this patch
> >
> >*.kernel.org/pub/linux/kernel/people/axboe/patches/v2.5/2.5.1/bio-251-1.bz2
> >
> >and ide-floppy should work again.
> >
> >
> Anyone have any patches for DAC960?  It doesn't compile, and I made the
> 
> "seemingly" obvious changes, but when I insmod, it sits in 
> "(initializing)".  This is on an Alpha AS1200 that I'm trying to use for 
> SPECsfs97 regression work...  Any ideas?

DAC960 will require some non-trivial work. I would do it, but reading
DAC960.[ch] makes my stomache bubble.

Note that it's not just buffer_head -> bio translation, it's also
walking the multi-page bios on your own (or better yet, transition it to
use blk_rq_map_sg) and adapting it to the pci dma mapping api.

-- 
Jens Axboe


  reply	other threads:[~2001-12-18 16:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8A43C34093B3D5119F7D0004AC56F4BCC3441C@difpst1a.dif.dk>
     [not found] ` <3C1F305C.9030702@t-online.de>
2001-12-18 14:30   ` bug in 2.5.1 Hans-Otto Ahl
2001-12-18 14:53     ` Jens Axboe
2001-12-18 16:27       ` Peter Rival
2001-12-18 16:44         ` Jens Axboe [this message]
2001-12-17 21:07 Hans-Otto Ahl

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=20011218174445.H32511@suse.de \
    --to=axboe@suse.de \
    --cc=frival@zk3.dec.com \
    --cc=linux-kernel@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.