[haiku] Re: Improving the hardware driver situation in Haiku

  • From: Brian Hague <alphaseinor@xxxxxxxxx>
  • To: haiku@xxxxxxxxxxxxx
  • Date: Sat, 17 Oct 2009 18:59:21 -0500

I'm with the agrees crowd, so lets  start the discussion... I'm not the most
active on the list, so bear with me.

From what I can tell, there are two generic  methods for doing this.
The first is to detect all known hardware in the driver list (run all
userland and systemland drivers, see what sticks)
The second is to scan all hardware locations, then assign drivers

IIRC, BeOS used something like the first. this would be the driver's
responsibility to report any errors upon load, or partial functionality
load. possibly have a detected failsafe driver for VESA fisrt, then try the
accelerated driver, and if the accelerated driver fails, then use VESA?

Brian Hague (alphaseinor)

On Sat, Oct 17, 2009 at 6:16 PM, Izomiac <haikulist@xxxxxxxxxxxxxxxx> wrote:

> I'm one of the "agrees" crowd.  I actually started to reply but after
> typing out the e-mail realized that I didn't have anything useful to add
> since you basically covered it and I realized that my ideas for possible
> implementations are pretty much the obvious way to do it.  So, as far as I
> can tell, Axel is right.
> On Sat, Oct 17, 2009 at 5:44 PM, Ryan Leavengood <leavengood@xxxxxxxxx>wrote:
>> On Sat, Oct 17, 2009 at 3:10 PM, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
>> wrote:
>> >
>> > I guess everyone agrees with that. It's just the question who does what
>> > and how - it would be nice to compile a short list of action items, and
>> > someone who feels responsible for each.
>> I was starting to wonder if this email had even reached the list since
>> no one had responded. I guess it is a reasonable list of things to
>> work on. Of course they are mainly suggestions, since at this point
>> drivers are not my area of expertise. If no one else ever works on it
>> and I have time in the future I can always take a look.
>> Of course if you guys want to make a list of action items and work on
>> it that is great too.
>> --
>> Regards,
>> Ryan

Other related posts: