From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Matt_Domsch@Dell.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk,
dougg@torque.net, jgarzik@mandrakesoft.com
Subject: Re: [PATCH] adding PCI bus information to SCSI layer
Date: Tue, 24 Apr 2001 15:59:50 -0600 [thread overview]
Message-ID: <200104242159.f3OLxoB07000@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <CDF99E351003D311A8B0009027457F140810E286@ausxmrr501.us.dell.com>
In-Reply-To: <CDF99E351003D311A8B0009027457F140810E286@ausxmrr501.us.dell.com>
Matt Domsch writes:
> Thanks everyone for your input again. I've made the changes suggested, and
> would appreciate this being applied to Linus' and Alan's trees. This is
> necessary for solving the "what disk does BIOS think is my boot disk"
> problem on IA-64, and I hope to extend it to IA-32 when BIOSs permit.
>
> Jeff Garzik recommended the IOCTL return pci_dev::slot_name, so now it does,
> and this simplifies the ioctl greatly.
> Doug Gilbert recommended wrapping things in #ifdef's, so I created a new
> CONFIG_SCSI_PCI_INFO define.
As I said to Matt privately, I think adding this kind of ioctl is
ugly. We have enough ioctl's as it is. All Matt is trying to do is to
access drives via location, so exposing location-based device nodes
via devfs is IMNSHO cleaner.
The plan I have (which I hope to get started on soon, now that I'm
back from travels), is to change /dev/scsi/host# from a directory into
a symbolic link to a directory called: /dev/bus/pci0/slot1/function0.
Thus, to access a partition via location, one would use the path:
/dev/bus/pci0/slot1/function0/bus0/target1/lun2/part3.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-04-24 22:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 21:02 Matt_Domsch
2001-04-24 21:59 ` Richard Gooch [this message]
2001-04-27 4:31 ` Richard Gooch
2001-05-01 1:27 ` Richard Gooch
2001-05-01 8:46 ` Ingo Oeser
2001-05-01 16:53 ` Richard Gooch
2001-05-01 20:32 ` Alan Cox
2001-05-02 15:03 ` Ingo Oeser
2001-05-02 15:54 ` Alan Cox
2001-05-03 8:57 ` Chris Wedgwood
2001-05-03 9:49 ` Alan Cox
2001-05-03 10:23 ` Chris Wedgwood
2001-04-24 23:16 ` Jonathan Lundell
2001-04-27 5:24 ` Jonathan Lundell
2001-05-01 14:38 ` Jonathan Lundell
2001-05-03 7:32 ` Kai Henningsen
2001-05-03 7:51 ` Jonathan Lundell
2001-05-11 16:32 ` Ralf Baechle
2001-05-11 23:00 ` Steven Willoughby
2001-05-11 22:49 ` Jonathan Lundell
2001-05-12 2:20 ` Ralf Baechle
2001-05-12 4:21 ` Jonathan Lundell
[not found] <p0510030db7221c090810@[10.128.7.49]=FE2>
2001-05-12 11:00 ` Kai Henningsen
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=200104242159.f3OLxoB07000@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=Matt_Domsch@Dell.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dougg@torque.net \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®