From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Thu, 4 Sep 2008 11:15:26 -0400 To: michaelian.ennis@gmail.com, 9fans@9fans.net Message-ID: <4b0884274c3eb8d5652e9b8a11ccad21@coraid.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Subject: Re: [9fans] apropos of the glendix post Topicbox-Message-UUID: 0d060f9c-ead4-11e9-9d60-3106f5b1d025 > Sometimes the binary bits are loaded into the cards, maybe most often, > and therefore can be done in plan9 as well. Depending on the vendor > you may need permission from them to distribute the binary part. cf. etherm10g.c. the myricom driver loads a metric ton of firmware into the card. > I suspect that some of these drivers are missing still because the > hardware is not available to the developers who can write them. > [...] > > I think the one of the BSD projects, OpenBSD perhaps, used to accept > hardware donations to this end. If we had a wayto get the hardware > and the technical documentation in the same place as the developers we > could get more hardware supported. good point. there's plenty of hardware out there with full documentation that's cheep. ati has fully documented the 2d in newer cards, for example. (a project i never seem to get to.) intel have done the same. there are also a number of cards that aren't really documented but seem straightforward anway — like the old nvidia propritary sata interface. if you have such a board and need >2 drives, this might be a fun and easy project. writing drivers is an interesting exercize. on the one hand, small errors will get you quickly because they typically run millions of times per second. this isn't all bad because one finds errors quite quickly. :-) on the other hand, they typically follow a small, constrained interface so it's easy to know when you're done and you don't need to design an interface. - erik