USB IDE Connector

USB IDE Connector

[Sumit Narayan]

Hi,

I have an external IDE connector through USB port. Where could I get
the exact point inside the kernel, from where I would get information
such as Block No., Request size, partition details for a particular
request, _just_ before being sent to the disk.

Like, for a normal IDE, I could gather these details from inside the
function __ide_do_rw_disk from "struct request". Is there anyway for
finding out the same for a USB mass storage device?

Thanks.

Re: USB IDE Connector

[Greg KH]

On Fri, Feb 25, 2005 at 10:30:27AM +0530, Sumit Narayan wrote:
> Hi,
> 
> I have an external IDE connector through USB port. Where could I get
> the exact point inside the kernel, from where I would get information
> such as Block No., Request size, partition details for a particular
> request, _just_ before being sent to the disk.
> 
> Like, for a normal IDE, I could gather these details from inside the
> function __ide_do_rw_disk from "struct request". Is there anyway for
> finding out the same for a USB mass storage device?

Why would you want to know this information for a controller device that
acts like a scsi one, not an IDE one (that's what usb storage devices
do...)

thanks,

greg k-h

Re: USB IDE Connector

[Sumit Narayan]

Well, basically I would like to test the file system. And since I
travel I lot, I carry laptop and this external disk with me. So, was
just wondering if I could somehow conduct a disk-level test.

Thanks.


On Fri, 25 Feb 2005 14:36:49 -0800, Greg KH <greg@kroah.com> wrote:
> On Fri, Feb 25, 2005 at 10:30:27AM +0530, Sumit Narayan wrote:
> > Hi,
> >
> > I have an external IDE connector through USB port. Where could I get
> > the exact point inside the kernel, from where I would get information
> > such as Block No., Request size, partition details for a particular
> > request, _just_ before being sent to the disk.
> >
> > Like, for a normal IDE, I could gather these details from inside the
> > function __ide_do_rw_disk from "struct request". Is there anyway for
> > finding out the same for a USB mass storage device?
> 
> Why would you want to know this information for a controller device that
> acts like a scsi one, not an IDE one (that's what usb storage devices
> do...)
> 
> thanks,
> 
> greg k-h
>