On Tue, Aug 10, 2010 at 01:53:47AM +, Alexander Best wrote:
hi there,
just wanted to get some feedback for this tiny patch and if people think it
makes sense.
I almost agree with the part of the patch that removes excessive commenting
for the individual signals. But I do not see much
On Tue Aug 10 10, Kostik Belousov wrote:
On Tue, Aug 10, 2010 at 01:53:47AM +, Alexander Best wrote:
hi there,
just wanted to get some feedback for this tiny patch and if people think it
makes sense.
I almost agree with the part of the patch that removes excessive commenting
for
Hi,
Here is a link to a blog post speaking about timing attacks.
http://rdist.root.org/2010/08/05/optimized-memcmp-leaks-useful-timing-differences/
It describes various memcmp() implementations of some OSes. FreeBSD is
mentionned at the end of the post and it warns about the fact that gcc
uses
On 2010-08-10 10:08, Clement LECIGNE wrote:
It describes various memcmp() implementations of some OSes. FreeBSD is
mentionned at the end of the post and it warns about the fact that gcc
uses its own builtin memcmp() function when optimization (from O1 to O3)
is set. Unfortunately the gcc
On Wednesday 04 August 2010 23:24:12 Neel Natu wrote:
Hi,
On Wed, Aug 4, 2010 at 12:29 PM, Hans Petter Selasky hsela...@c2i.net
wrote:
On Wednesday 04 August 2010 21:13:55 Neel Natu wrote:
Hi,
On Wed, Aug 4, 2010 at 10:18 AM, Hans Petter Selasky hsela...@c2i.net
wrote:
Hi,
I'm looking into a clean, permanent solution for WD Green drives that
use 4096-byte physical sectors. To summarize the information I've
collected so far:
- There are several types of WD Green disks. I am primarily interested
in the 1+ TB models: EARS and EADS.
- According to WD's own
On Tue, 10 Aug 2010 19:44:48 +0200 =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=
d...@des.no wrote:
I'm looking into a clean, permanent solution for WD Green drives that
use 4096-byte physical sectors. To summarize the information I've
collected so far:
- There are several types of WD Green
Is there truly no IDENTIFY information to determine the drive format?
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Bakul Shah ba...@bitblocks.com writes:
http://www.wdc.com/en/library/2579-001028.pdf gives an
explanation of what the drive letters mean but they don't
talk about 4k sector size.
The latest data sheet for the entire Green series is here:
After poking around some, it seems ATA/ATAPI-7 Identify
Device word 106 bit 13 is set to 1 and bits 0-3 are set to 3
(for 2^3 or 8 LBAs per sector) for a 4KB sector size (pin 7-8
jumper on a WD AF disks presumably changes this setting to
0,0). See page 121 of Atapi-7 volume 1 (google for
src/usr.bin/netstat/if.c was modified back in late November 1995, to
expand the Network field from 11 characters to 13:
| Revision 12459 - (view) (annotate) - [select for diffs]
| Modified Wed Nov 22 22:21:04 1995 UTC (14 years, 8 months ago) by se
| File length: 11619 byte(s)
| Diff to previous
Yes, that should be it!
After poking around some, it seems ATA/ATAPI-7 Identify
Device word 106 bit 13 is set to 1 and bits 0-3 are set to 3
(for 2^3 or 8 LBAs per sector) for a 4KB sector size (pin 7-8
jumper on a WD AF disks presumably changes this setting to
0,0). See page 121 of Atapi-7
On 11.08.2010 2:50, Bakul Shah wrote:
After poking around some, it seems ATA/ATAPI-7 Identify
Device word 106 bit 13 is set to 1 and bits 0-3 are set to 3
(for 2^3 or 8 LBAs per sector) for a 4KB sector size (pin 7-8
jumper on a WD AF disks presumably changes this setting to
0,0). See page
13 matches
Mail list logo
