> Date: Mon, 2 May 2016 14:25:51 +1000 > From: Jonathan Gray <[email protected]> > > On Sun, May 01, 2016 at 11:21:18PM +0200, Mark Kettenis wrote: > > Diff below provides a bit more meaningful information in the SCSI > > INQUIRY emulation. It decodes the JDEC manufacturer ID code and > > provides the product string and revision number as read from the card. > > > > For example: > > > > scsibus1 at sdmmc2: 2 targets, initiator 0 > > sd0 at scsibus1 targ 1 lun 0: <Sandisk, SA04G, 0006> SCSI2 0/direct fixed > > sd0: 3768MB, 512 bytes/sector, 7716864 sectors > > scsibus2 at sdmmc0: 2 targets, initiator 0 > > sd1 at scsibus2 targ 1 lun 0: <Kingston, S10032, 0000> SCSI2 0/direct fixed > > sd1: 29184MB, 512 bytes/sector, 59768832 sectors > > > > where sd0 is an SD card and sd1 is the eMMC soldered onto the board of > > the machine. > > > > Note that the strncpy here is safe. The strings in the scsi inquiry > > page don't have to be nul-terminated. > > > > ok? > > Sounds good to me though you don't seem to have mids for > any of the cards I have, only one of the emmc devices. > > I wonder if it is worth skipping the product if it is > all '0'/' ' > > 0x03 SanDisk > 0x1b Samsung > 0x28 Lexar (Micron) > 0x45 SanDisk
Already added the 0x45 SanDisk one. Would like some sort of confirmation on the others. The label on the card doesn't always correspond to the actual manufacturer of the card. > sandisk 4GB SD > unknown MID 0x3 > sd1 at scsibus2 targ 1 lun 0: <SD/MMC, SD04G, 0080> SCSI2 0/direct fixed > sd1: 3781MB, 512 bytes/sector, 7744512 sectors Although this one probably is genuine SanDisk.
