From: "Robert Mueller" <robm@fastmail.fm>
To: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: "Andrew Morton" <akpm@digeo.com>, "Dax Kelson" <dax@gurulabs.com>,
"James Bottomley" <James.Bottomley@SteelEye.com>,
"Bron Gondwana" <brong@fastmail.fm>, "erich" <erich@areca.com.tw>,
"Christoph Hellwig" <hch@infradead.org>,
"Randy.Dunlap" <rdunlap@xenotime.net>
Subject: Areca driver recap + status
Date: Thu, 22 Jun 2006 14:18:23 +1000 [thread overview]
Message-ID: <09be01c695b3$2ed8c2c0$c100a8c0@robm> (raw)
Hi
As happy users of areca raid cards, we're keen to see a stable driver make
it into the next kernel release. I thought I might quickly recap what's
happened with the driver over the last 6 months to see where things are at:
The driver went into 2.6.11-rc3-mm1 here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=110754432622498&w=2
A thread about overall style + api problems here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113525798005993&w=2
Some specific comments + patches from Randy and Chris about problems:
http://marc.theaimsgroup.com/?l=linux-scsi&m=113597128115672&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=114045972531035&w=2
An update from erich went into 2.6.16-rc6-mm2 to address a number of the
problems:
http://marc.theaimsgroup.com/?l=linux-kernel&m=114282535310724&w=2
End of thread about problem ARCMSR_MAX_XFER_SECTORS of 4096 vs 512:
http://marc.theaimsgroup.com/?l=linux-kernel&m=114602195422443&w=2
Comment from Andrew about helping to get the driver in:
http://marc.theaimsgroup.com/?l=linux-kernel&m=114945466405532&w=2
Though there did still seem to be quite a few things missing:
http://marc.theaimsgroup.com/?l=linux-scsi&m=114556263632510&w=2
General comment on areca driver is "improving", we seem to need a sound
"todo" list:
http://marc.theaimsgroup.com/?l=linux-kernel&m=114949920416720&w=2
Some of those remaining problems seem pretty serious concerns, though I
don't really know any of the technical details. The latest driver from -mm
seems to be working well for us at the moment. Is the general concensus that
the driver should go in despite these issues, and they can be fixed over
time? Or are these still show stoppers?
Thanks
Rob
next reply other threads:[~2006-06-22 4:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 4:18 Robert Mueller [this message]
2006-06-22 5:28 ` Areca driver recap + status Andrew Morton
2006-06-22 6:35 ` Jeff Garzik
2006-06-26 14:48 ` James Bottomley
2006-06-26 15:01 ` Andrew Morton
2006-07-07 8:41 ` erich
2006-07-07 9:04 ` Andrew Morton
2006-06-26 22:32 ` Robert Mueller
2006-06-27 15:27 ` James Bottomley
2006-06-27 15:51 ` Alan Cox
2006-06-27 15:39 ` James Bottomley
2006-06-27 16:36 ` Alan Cox
2006-06-27 0:23 ` Dax Kelson
2006-06-27 15:27 ` James Bottomley
2006-06-27 9:47 ` erich
2006-06-27 16:12 ` James Bottomley
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='09be01c695b3$2ed8c2c0$c100a8c0@robm' \
--to=robm@fastmail.fm \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@digeo.com \
--cc=brong@fastmail.fm \
--cc=dax@gurulabs.com \
--cc=erich@areca.com.tw \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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