From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Vendor field with USB, [SP]ATA etc-attached disks
Date: Tue, 12 Sep 2006 21:42:51 +0900 [thread overview]
Message-ID: <4506AB4B.9010801@gmail.com> (raw)
In-Reply-To: <4505BA2B.1020105@garzik.org>
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
next prev parent reply other threads:[~2006-09-13 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 18:08 Vendor field with USB, [SP]ATA etc-attached disks Michael Tokarev
2006-09-11 19:34 ` Jeff Garzik
2006-09-12 12:42 ` Tejun Heo [this message]
2006-09-13 1:22 ` Jeff Garzik
2006-09-13 1:28 ` Tejun Heo
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=4506AB4B.9010801@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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