So it appears that the firmware implementation has chosen to support Block I/O
for the SCSI controller you are working with and not expose SCSI I/O, which is
legal (it boots, right?) but not very helpful for your explorations. This can
happen when the low-level SCSI support is a legacy option ROM (with ASPI, for
example). Rather than trying to create a SCSI_IO<->ASPI layer, they just
abstracted one layer higher.
From: Sushma Gurram [mailto:sushma.gur...@sandisk.com]
Sent: Friday, August 24, 2012 10:33 AM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] SCSI Protocols not found
Hi Feng,
The screenshots seem to have increased the email size.
In any case, what I see is the following:
Handle of the device is 184 which shows up as Scsi in the device path :
PciRoot(0x0)/Pci(0x3,0x2)/Pci(0x0,0x0)/Scsi(0x9,0x0)
Controller Type : BUS
Protocols installed are : DiskIo, BlkIo
Managed By : Drv[E2] - Image(FvFile(5ae3f37e-4eae-41ae-8240-35465b5e81eb))
Drv[E6] -
Image(FvFile(5ae3f37e-4eae-41ae-8240-35465b5e81eb))
Driver with handle E2 is a Device Driver with DriverName "Unknown" and
ImageName "CORE_DXE"
Driver with handle E6 is a Bus Driver with DriverName "Unknown" and ImageName
"CORE_DXE"
Thanks,
Sushma
From: Sushma Gurram
Sent: Friday, August 24, 2012 10:21 AM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: RE: SCSI Protocols not found
Hi Feng,
Attached are a few screenshots for different shell command dumps.
drivers-1.gif, drivers-2.gif : List of all modules loaded
devices-gif : shows the SCSI device with handle 184
dh-1.gif : shows all information associated with the device handle 184, the
protocols installed, controller type and drivers which manage the device. >From
this dump, it appears that Drivers with handle E2 and E6 manage this device.
Looking up E2 and E6 in "drivers" dump has the Driver Name as "unknown" and
Image Name as "CORE_DXE".
Can you please let me know what to infer from the above?
Thanks,
Sushma
From: Tian, Feng
[mailto:feng.t...@intel.com]<mailto:[mailto:feng.t...@intel.com]>
Sent: Thursday, August 23, 2012 7:53 PM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: Re: [edk2] SCSI Protocols not found
Could you show me which modules are loaded by executing "drivers" cmd?
From: Sushma Gurram
[mailto:sushma.gur...@sandisk.com]<mailto:[mailto:sushma.gur...@sandisk.com]>
Sent: Friday, August 24, 2012 05:12
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: Re: [edk2] SCSI Protocols not found
I'm trying to dump handles (globally) by protocol using shell command
Shell> dh -p scsiio
Shell> dh -p extscsipassthru
Shell> dh -p scsipassthru
No handles are returned.
Programatically using the LocateProtocol() service function
Status = gBS->LocateProtocol(&gEfiScsiPassThruProtocolGuid, NULL,
(VOID**)&gScsiPassThru);
The above function returns "Not Found" status.
Thanks,
Sushma
From: Tim Lewis
[mailto:tim.le...@insyde.com]<mailto:[mailto:tim.le...@insyde.com]>
Sent: Thursday, August 23, 2012 2:01 PM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: Re: [edk2] SCSI Protocols not found
Susha -
Just to make sure: The actual SCSI device would be at:
PciRoot(0x0)/Pci(0x3,0x2)/Pci(0x0,0x0)/Scsi(0x9,0x0)
(without the /HD(1,MBR,0xc64a382f,0x800,0x1749e000), which is the partition on
the disk)
So that would be a different handle.
Tim
From: Sushma Gurram
[mailto:sushma.gur...@sandisk.com]<mailto:[mailto:sushma.gur...@sandisk.com]>
Sent: Thursday, August 23, 2012 1:57 PM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: [edk2] SCSI Protocols not found
Hi,
We have a drive which shows up as a SCSI device when "map" shell command is
executed.
The device path for the device is as follows:
PciRoot(0x0)/Pci(0x3,0x2)/Pci(0x0,0x0)/Scsi(0x9,0x0)/HD(1,MBR,0xc64a382f,0x800,0x1749e000).
We need to issue SCSI INQUIRY and other SCSI commands to the device.
However, none of the SCSI protocols - EFI_SCSI_IO_PROTOCOL,
EFI_SCSI_PASS_THRU_PROTOCOL, EFI_EXT_SCSI_PASS_THRU_PROTOCOL are found on the
setup when queried using "dh -p " shell command.
Can someone provide input on why the protocols don't exist and how to issue
SCSI commands to the device?
Thanks,
Sushma
________________________________
PLEASE NOTE: The information contained in this electronic mail message is
intended only for the use of the designated recipient(s) named above. If the
reader of this message is not the intended recipient, you are hereby notified
that you have received this message in error and that any review,
dissemination, distribution, or copying of this message is strictly prohibited.
If you have received this communication in error, please notify the sender by
telephone or e-mail (as shown above) immediately and destroy any and all copies
of this message in your possession (whether hard copies or electronically
stored copies).
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
