<br><br><div><span class="gmail_quote">On 8/29/07, <b class="gmail_sendername">Uwe Hermann</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, Aug 27, 2007 at 05:21:08PM -0500, Corey Osgood wrote:<br>> > We had such calls before, and people would send in their board<br>> > information, assuming that this would be enough for us to support their
<br>> > hardware. Unfortunately not a single new port resulted from this, though<br>> > many people participated and lots of (unaccomplished) expectations were<br>> > created. So I carefully wonder what the real goal of such a call would
<br>> > be, except gathering random people with random boards?<br>><br>> Well, that's how I found this place, and that resulted in one port (so<br>> far) :) But I can very clearly see your point.<br><br>
What exactly lead you to this project? That would be interesting to<br>analyze...<br><br>My feeling is that a "post your lspci" call for action will result in<br>lots of lspci's (which is totally useless) and we'll have to tell all
<br>those people "no, your board/chipset is not yet supported". That sucks,<br>and there's really no gain in doing that.<br><br>Now, what I think would indeed be useful is a Call For Developers.<br>Because that's what we really need, more developers, more man-power
<br>to actually write code to support new chipsets.<br>Random lspci's from random people don't help at all. We've had tons of<br>those already and they all end up with "no, it's not supported" answers.
<br><br><br>> > Something like:<br>> > We have 10 people who are willing to work on this or that mainboard if<br>> > you get them a system they can keep for doing the work, given that the<br>> > northbridge and southbridge are already supported... Other ideas?
<br><br>Won't help either. The number of active developers doing new ports is<br>way less than 10 anyway. Personally I have at least 4-5 board sitting<br>here which should be relatively easy to support, I'm just lacking the
<br>required spare time.<br><br>We need more developers and/or more time.<br><br>I don't think money is a problem in most cases (if it is we can probably<br>arrange for some hardware shipping or ask for donations or something).
<br><br>The real problems (in my view) are:<br><br> 1. Lack of developers<br> 2. Lack of time<br> 3. Lack of proper datasheets (for some/many chipsets)<br><br>Issue 2 cannot be solved easily, issue 3 depends on many factors
<br>we usually cannot influence a lot, but issue 1 is where we can<br>get the biggest gain, IMHO.<br></blockquote></div><br>I wonder if clean-room reverse engineering on commercial BIOS that comes <br>with the board can help for case 3 because most of them have a "generic"
<br>code to boot the machine until preliminary RAM test. Personally, I view it <br>as a *very interesting* challenge. <br><br><br>Regards,<br><br>Darmawan Salihun<br>--------------------------------------------------------------------
<br>-= Human knowledge belongs to the world =-