From: safemode <safemode@speakeasy.net>
To: Mikael Pettersson <mikpe@csd.uu.se>, ionut@cs.columbia.edu
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH,RFC] make ide-scsi more selective
Date: Sat, 25 Aug 2001 13:33:58 -0400 [thread overview]
Message-ID: <20010825173350Z269909-760+5944@vger.kernel.org> (raw)
In-Reply-To: <200108251210.OAA25028@harpo.it.uu.se>
In-Reply-To: <200108251210.OAA25028@harpo.it.uu.se>
On Saturday 25 August 2001 08:10, Mikael Pettersson wrote:
> On Sat, 25 Aug 2001 02:56:20 -0400 (EDT), Ion Badulescu wrote:
> >I've concocted another patch, which includes my previous one and
> >implements Mikael's idea somewhat more consistently. It adds another
> >option, "noscsi", so that by saying hdX=noscsi on the kernel command line
> >the user can prevent the ide-scsi driver from ever claiming that drive.
> >
> >So:
> >- by default it's first come, first served
> >- hdX=scsi means only the ide-scsi driver can claim hdX
> >- hdX=noscsi means the ide-scsi driver must not claim hdX ever
> >
> >Sounds good? If so, please apply, it makes many CDR users' lives easier.
>
> Looks fine to me. Tested briefly and it does get the job done.
>
> /Mikael
>
> p.s. anyone know if cdrecord will ever support ATAPI CDRs natively?
> -
> 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/
Is there something wrong with making the Atapi cdrom driver as module and
then loading that with an ignore hdX then loading the ide-scsi module? That
doesn't seem hard at all. just two pretty lines in /etc/modules. Just make
both drivers modular. otherwise you have people needing to do boot
arguments through lilo.
and andre had a patch at one time that was supposed to do something like
allow you to use the recording function of ide CDR's without the scsi layer.
Not sure if it was complete or even really working but i tried it once.
Maybe you can ask him if it's possible.
next prev parent reply other threads:[~2001-08-25 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-25 12:10 Mikael Pettersson
2001-08-25 12:37 ` André Dahlqvist
2001-08-25 17:33 ` safemode [this message]
[not found] <200108251734.NAA28426@cs.columbia.edu>
2001-08-27 14:37 ` Ion Badulescu
-- strict thread matches above, loose matches on Subject: below --
2001-08-22 23:51 Chris Rankin
2001-08-22 22:37 Torrey Hoffman
[not found] <no.id>
2001-08-22 21:17 ` Alan Cox
2001-08-22 21:53 ` Nicholas Knight
2001-08-22 22:00 ` Ion Badulescu
2001-08-22 22:39 ` Nicholas Knight
2001-08-23 3:42 ` mhobgood
2001-08-23 3:54 ` Ion Badulescu
2001-08-23 4:29 ` Nicholas Knight
2001-08-23 0:12 ` Willem Riede
2001-08-25 6:56 ` Ion Badulescu
2001-08-22 19:46 Mikael Pettersson
2001-08-23 2:49 ` Keith Owens
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=20010825173350Z269909-760+5944@vger.kernel.org \
--to=safemode@speakeasy.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ionut@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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
all inboxes | Powered by JetHome®