In message <[EMAIL PROTECTED]>, Nate Lawson writ
es:
>On Mon, 4 Nov 2002, Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, Nate Lawson writ
>> es:
>> >It might be more useful for GEOM to query the BIOS for the physical values
>> >and provide a way for upper levels (like CAM) to retrieve
In message <[EMAIL PROTECTED]>, Nate Lawson writ
es:
>It might be more useful for GEOM to query the BIOS for the physical values
>and provide a way for upper levels (like CAM) to retrieve this.
This is a driver task. besides GEOM is above CAM, not below it.
--
Poul-Henning Kamp | UNIX si
In message <[EMAIL PROTECTED]>, John Hay wri
tes:
>>
>> Let's work on the 'proper' solution first.
>>
>> What SCSI commands are suitable for getting the geometry, generically
>> on a device?
>
>Hmmm, I made an interesting discovery. I searched through some of the
>scsi drivers, sys/dev/{aha|ahb|a
>
> Let's work on the 'proper' solution first.
>
> What SCSI commands are suitable for getting the geometry, generically
> on a device?
Hmmm, I made an interesting discovery. I searched through some of the
scsi drivers, sys/dev/{aha|ahb|aic*|sym}, looking for XPT_CALC_GEOMETRY
and they all fake
> > Well the short version of the problem is that "fdisk -BI " works
> > on -stable to get a FreeBSD partition on the Compact Flash. This does
> > not work on -current anymore. I have traced that back to the commit
> > in umass.c rev 1.61 that removed the fake geometry setting and just
> > leave th
>
> USB is only the transport. It doesn't add or remove functionality (the
> only exception being probing for LUNs on CBI devices). If you want to
> determine the geometry you will have to do this through SCSI commands. I
> was hoping that the CAM code would be smart enough to request the
> detail
In message <[EMAIL PROTECTED]>, John Hay wri
tes:
>> : Hmmm. I just noticed that the disks probe with zero values for the
>> : heads, sectors/track and cylinders. I have tried two different USB
>> : CF readers and both do it. On 4.x it probes with the correct values
>> : on the same machine and the
> : Hmmm. I just noticed that the disks probe with zero values for the
> : heads, sectors/track and cylinders. I have tried two different USB
> : CF readers and both do it. On 4.x it probes with the correct values
> : on the same machine and the same devices. So why do they probe
> : wrong?
>
> Do
