[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4506AB4B.9010801@gmail.com>
Date: Tue, 12 Sep 2006 21:42:51 +0900
From: Tejun Heo <htejun@...il.com>
To: Jeff Garzik <jeff@...zik.org>
CC: Michael Tokarev <mjt@....msk.ru>,
Linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Vendor field with USB, [SP]ATA etc-attached disks
Jeff Garzik wrote:
> Michael Tokarev wrote:
>> With current SATA, PATA and at least some USB disks,
>> Linux reports Vendor: $subsystem, instead of the actual
>> vendor of the drive, like this:
>>
>> scsi1 : ata_piix
>> Vendor: ATA Model: ST3808110AS Rev: n/a
>> Type: Direct-Access ANSI SCSI revision: 05
>>
>> This should be Vendor: Seagate, not ATA (Note also the lack
>> of "Revision" field). The same for PATA disk:
>>
>> scsi0 : pata_via
>> Vendor: ATA Model: ST3120026A Rev: 3.76
>> Type: Direct-Access ANSI SCSI revision: 05
>>
>> The same is shown in /sys/block/$DEV/device/vendor.
>>
>> Can it be changed to show real vendor, instead of the subsystem name?
>
> No. Two reasons:
>
> * ATA doesn't export the vendor separate from the model, and in some
> cases (Seagate) it isn't present at all, anywhere.
> * "ATA" vendor string is the standardized value to put in that field,
> according to the SCSI T10 specifications.
To add a small detail. The reason it's printed that way is because
libata (the new ATA driver) emulates SCSI device at the moment, so it
has to fake SCSI vendor ID and model string, which BTW is shorter than
ATA string and thus truncated in some cases. The vendor ID "ATA" is
defined in SAT (SCSI ATA translation) standard, IIRC.
For the time being, we'll have to live with boilerplate ATA vendor and
truncated vendor ID. There are plans to make libata independent from
SCSI which should solve the problem but it will take quite some time.
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists