[interfacekit] Re: App Server Startup procedures and question

Yeah, I followed a very interesting discussion between Michael Phipps
and Travis Geiselbrecht on IRC yesterday speaking about this very issue
(iterating through all drivers).  Seems to me that the easiest thing to
do would be:

* On first boot, iterate all drivers
* Cache the successfully loaded driver
* On subsequent boots, directly load the driver
* If loading the cached driver fails, start from the top

Which I guess is essentially what you're suggesting we do. =P

Of more concern to me were these statements that Travis made:

<geist> The best part of BeOS is the app server. It is pure genious
<geist> I'm extremely interested in what openbeos comes up with. :) 
<geist> the app_server is not pretty but it is crazy fast
<geist> it's by far more complex than any other piece of the system,
including the kernel

It's nice to know what people's expectations are, anyway.  No pressure,
guys. ;P

e

Yuri Titov wrote:
> 
> > > as for everything else, it sounds right to me.  also dont know if you
> > > thought about this but once it finds the non-vesa driver that works, it
> > > should call B_OPEN_GRAPHICS_CARD on that driver on the next bootup.
> >
> > I see what you're trying to do with this, but I don't think it's
> > strictly necessary (the process of loading an addon, checking to see if
> > it works and unloading it is very fast), and makes it less easy for the
> > system to magically "discover" that you've replaced your video card.
> > This is of the things I absolutely love about BeOS -- swap out hardware,
> > and if there's a driver for it, it just works when you reboot. =)
> >
> yeah this was purely forward looking once openbeos comes with around 100
> video drivers so hehe.
> 
> -yt

Other related posts: