Re: Limitations Within a Driver
Re: Limitations Within a Driver
- Subject: Re: Limitations Within a Driver
- From: Godfrey van der Linden <email@hidden>
- Date: Mon, 26 Nov 2001 16:56:47 -0800
Sean this project of yours is definitely going around in circles.
Can you describe in great detail the problem you are trying to solve
and lets see if we can find a clean design for you.
X has any number of mechanismns that can provide the sort of services
you want but there is usually one or two mechanisms that stand out
once the problem is clearly defined.
So I can assume you wish to write a X Audio driver framework that
will be in some manner software configurable.
What are you trying to do at configuration time?
Godfrey
At 11:20 -0800 01-11-26, Sean Morrell wrote:
email@hidden writes:
You can probably get this to work, but I think, in general, it's A Bad
Idea. What, exactly, are you trying to achieve?
Oh, I was just looking for another way of configuring my device driver
from user space. The sysctl mechanism was suggested by a gentlemen a few
days ago. But I don't believe it will work in my situation. This device
is one of a series. Several devices of the same model can be connected on
a single system. And there is no way of identifying each device uniquely,
other than USB address. So I would need a set of settings for every
(model, USB address). I don't see sysctl being applicable here. Tell me
if I'm wrong. I just thought it might be easier to have the configuration
done via a pipe or message queue. Any suggestions?
Regards,
>Justin