public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Arjan van de Ven <arjan@fenrus.demon.nl>,
	Paul Flinders <P.Flinders@ftel.co.uk>,
	linux-kernel@vger.kernel.org, Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: Help with Fasttrack/100 Raid on Linux
Date: Wed, 25 Apr 2001 17:10:40 +0200	[thread overview]
Message-ID: <3AE6E8F0.BCD74256@gmx.at> (raw)
In-Reply-To: <Pine.LNX.4.10.10104212104160.627-100000@master.linux-ide.org>

Hello Andre,

Sorry for responding a little late. I spent some time in the big blue
room (not that is was that blue lately!).

Andre Hedrick wrote:
> 
> On Wed, 18 Apr 2001, Wilfried Weissmann wrote:
> 
> > > off to the head or tail of the drive and get me that raid-voodoo-bios-os
> > > communication transport layer, and do it ins DMA modes, NOW!"
> >
> > "voodoo" would be the sector where the raid configuration is stored
> > then, right!? Maybe I did not understand you properly...
> 
> We are on the same page, good.

OK, and here it is (I extracted this out of the *BSD ata-raid.h):

This is the hpt-raid config block located at offset 0x1220 (sector 9).
All data is stored in little endian format.

0x0020 32 bits; magic cookie
	0x5a7816f0 for good array
	0x5a7816fd for bad array

0x0024 32 bits; raid volume cookie
	used to distinguish between raid volumes

0x0028 32 bits; raid-10 volume cookie ???

0x002C 32 bits; order bitmask
	0x04 status is OK
	0x02 striping
	0x01 mirroring
	Note: bits 0 and 1 appear to matter only in raid 10

0x0030 8 bits; disks in array

0x0031 8 bits; chunksize (1U << (*this+9))

0x0032 8 bits; raid level
	0x00 raid 0
	0x01 raid 1
	0x02 raid 10 & raid 0 (not supported)
	0x03 span
	0x04 raid 3 (not supported)
	0x05 raid 5 (not supported)
	0x06 single disk
	0x07 raid 10 & raid 1 (not supported)
	Note: raid 10 is done with raid level = raid 0 and order = ( mirroring
| striping )

0x0033 8 bits; disk number in array

0x0034 32 bits; raid volume size in sectors

0x0038 32 bits; disk mode ???

0x003C 32 bits; boot mode ???

0x0040 8 bits; boot disk ???

0x0041 8 bits; boot protect ???

0x0042 8 bits; error log entries

0x0043 8 bits error log index

0x0044 32x error entries
	32 bits; timestamp
	8 bits; reason (0xFF=broken, 0xFE=removed)
	8 bits; disk
	8 bits; status
	8 bits; sectors
	32 bits; lba

Mine looks like this:
001220 f0 16 78 5a b3 04 b3 84 00 00 00 00 04 00 00 00
001230 02 05 00 00 c0 2a 28 07 00 00 00 00 78 56 34 12
001240 a5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
001250 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
This is the signature of the first disk in a raid0 with 2 30GB disks and
16k chunk size.


Everything related to raid 10 is a bit weird, and I am not sure if the
BSD code is 100% accurate there. I am goint to install Abit's Gentus on
my system. This distro states that it supports most Abit hw quite well.
Maybe there is some good sourcecode somewhere...

[snip]

> > > I do not have the desire to do personality tables, but I can.
> 
> > > With about 96% of all linux boxes in the world dependent on some form of
> > > ATA/ATAPI, Linus and Alan are very sensitive to even the sligthest change.
> >
> > I would avoid to change anything there, but do a raid personality...
> > Well, we are back at our your solution vs. my raid personality
> > discussion again!
> 
> No we are back to your "raid personality", and a functional API to the
> ATA driver.

So you want that an ata raid level reuses the existing raid code?

> This is probably the first and last time I will openly agree for someone
> to tell me were to go, and do it ;-).

Well, I guess that is the reason why people keep kicking and banning me
from IRC channels...

> You tell me what you want the driver to do, and I will make it happen.
> It will be legal and technically correct.  Does that sound like a good
> idea?

Perfect! Since FreeBSD supports that controller, do you think Highpoint
would provide us "offical" documentation? Or do you already have some?

Do you want to have a look at my module? As I said only raid 0 is
implemented, but anyway...

I try to get written down what HPT would need from the API in hard
facts.

bye,
Wilfried

-- 
Wilfried Weissmann ( mailto:Wilfried.Weissmann@gmx.at )
Mobile: +43 676 9444465

  reply	other threads:[~2001-04-25 15:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3AD64568.28E170B6@mediaone.net>
2001-04-13  4:01 ` Help with Fasttrack/100 Raid on Linux Andre Hedrick
2001-04-13  8:09   ` Paul Flinders
2001-04-13 19:35     ` Arjan van de Ven
2001-04-13 22:15       ` Erik van Asselt
2001-04-16 20:33       ` Wilfried Weissmann
2001-04-16 20:51         ` Andre Hedrick
2001-04-17 12:14           ` Wilfried Weissmann
2001-04-18  2:44             ` Andre Hedrick
2001-04-18 20:05               ` Wilfried Weissmann
2001-04-19 16:39                 ` Wilfried Weissmann
2001-04-22  4:10                 ` Andre Hedrick
2001-04-25 15:10                   ` Wilfried Weissmann [this message]
     [not found] <3AD62556.7A35DF69@mediaone.net>
2001-04-12 22:34 ` Andre Hedrick
2001-04-13  0:14   ` Tim Moore
2001-04-13  0:26     ` Alan Cox

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=3AE6E8F0.BCD74256@gmx.at \
    --to=wilfried.weissmann@gmx.at \
    --cc=P.Flinders@ftel.co.uk \
    --cc=andre@linux-ide.org \
    --cc=arjan@fenrus.demon.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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