best way to determine devices with drivers

[andrew luecke]

Firstly, thanks for responding about my problem. Until now I just assumed 
that modules like USB printers etc which come with the kernel would fill 
that field, but now, after you mentioned cameras, I think you scratched that 
plan ;)

Maybe I'll also need to develop a database that can record userspace progs 
and drivers for devices or something.. guess it just got more complex.

Thanks for the feedback on the linux.drivers field though..  I was getting 
paranoid that I might have been going blind or something.

Auzy

>From: David Zeuthen <david at fubar.dk>
>To: andrew luecke <auzy1 at hotmail.com>
>CC: hal at freedesktop.org
>Subject: Re: best way to determine devices with drivers
>Date: Mon, 21 Jun 2004 01:27:59 +0200
>MIME-Version: 1.0
>Received: from tux.fubar.dk ([212.242.145.51]) by mc10-f7.hotmail.com with 
>Microsoft SMTPSVC(5.0.2195.6824); Sun, 20 Jun 2004 16:17:29 -0700
>Received: from [127.0.0.1] (tux.fubar.dk [127.0.0.1])by tux.fubar.dk 
>(Postfix) with ESMTPid A84CD533C9; Mon, 21 Jun 2004 01:27:59 +0200 (CEST)
>X-Message-Info: JGTYoYF78jEN68dQK0RkfyRk17ZE/BA2
>In-Reply-To: <BAY12-F73wa657thltb0005e49b at hotmail.com>
>References: <BAY12-F73wa657thltb0005e49b at hotmail.com>
>Message-Id: <1087774079.10645.87.camel at tux.fubar.dk>
>X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Return-Path: david at fubar.dk
>X-OriginalArrivalTime: 20 Jun 2004 23:17:29.0515 (UTC) 
>FILETIME=[C1C9DFB0:01C4571C]
>
>On Mon, 2004-06-14 at 11:00, andrew luecke wrote:
> > Hey all.
>
>Heya,
>
>sorry for the delay,
>
> > currently I'm working on a driver install system for linux, which
> > I'm hoping may one day help complement other linux usability projects, 
>that
> > automatically finds drivers on the internet for devices that dont 
>already
> > have them installed.
> >
>
>Interesting.
>
> > My problem is that to use HAL, I need a way of determining if a device
> > already has a driver installed and is active (so I can tell if I need to
> > install one). I have noticed under 0.2.92 that  there is a namespace I 
>can
> > use called "linux.driver".. However, I noticed when I ran lshal on my
> > devices that not even one of them had linux.driver listed.. So, does 
>anyone
> > know if this is the best way, or is there a better way (I noticed that 
>HAL
> > device manager listed my USB camera with no driver as an unknown 
>device).
> >
>
>Just to clarify, the meaning of linux.driver would be to indicate what
>kernel space driver is attached to the device; if your USB camera is
>handled by libgphoto probably no driver would be attached and
>linux.driver would not exist or be empty. HAL on FreeBSD, would probably
>expose freebsd.driver with the same semantics :-)
>
> > Any idea if its just because nothing is using the linux.driver flag yet,
> > lshal isn't listing it, or/and any better methods of determining if the
> > driver is working (info.not_available maybe??)
> >
>
>The linux.driver property used to be there before I rewrote some of the
>code, but I removed it for some reason, IIRC it's because HAL uses an
>old local copy of libsysfs that doesn't expose this for some reason. It
>makes sense to put it back in, but it will probably require an upgrade
>of the libsysfs sources in the HAL tree; shouldn't be too much work
>though.
>
>Cheers,
>David
>

_________________________________________________________________
Looking to buy a new house? Try   http://property.ninemsn.com.au/


_______________________________________________
hal mailing list
hal at freedesktop.org
http://freedesktop.org/mailman/listinfo/hal