As a quick comment:
The device ID is indeed fixed, this is the "old fashioned" way of
assigning device IDs.
In recent desktop linux environments the major number is now normally
configurable, the linux-fusion driver should be updatable to support
that. Note that some embedded devices do not support this, and embedded
systems in general do not suffer as strongly from major number clogging
as desktop systems. Open for patches though..
Greets
Niels
Mark wrote:
Hi,
On my system i use OSS and i just installed the linux-fusion module.
When i loaded the module this error came (from dmesg):
fusion: unable to get major 250
And when looking that one up in /proc divices it returns:
250 oss_hdaudio
Now my "fix" was to disable oss (soundoff) then modprobe fusion
followed by enabling oss again (soundon). oss now just took another
device id.
Now i told the oss fellows this issue on irc (freenode #oss) and they
say oss might be a bit to eager with device id's but linux-fusion
might prevent issues like this if they didn't forced the device id to
be 250:
http://git.directfb.org/?p=core/linux-fusion.git;a=blob;f=linux/drivers/char/fusion/fusiondev.c#l60
That's it as far as i know.
Note: directfb + linux-fusion _need_ a bug tracker!
Good luck,
Mark
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
--
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
