somebody who will read the following must forgive me first,because it came
from a really newbie and perhaps will bore you 
Thanx the help from the edlk,iron and other people who helped me,now I can
partioion and install multi-OS in my HD,and also can I do the file
manipulation and learn to give up installing my WINMODEM in QNX^-^.But
really more helps are needed for my going on the QNX.
I am thinking how the QNX install and use an audio device?Now I suppose
that:
when QNX is booting,it will scan all the devices on the host computer,if it
find a audio device and a matched driver existing,it will active a process
that use the audio driver to process the audio message from other process,am
I right?if I am right,my confusion is:
1,who will scan the device?the Neutrino or other manager?
2,how does the QNX decide which driver shall match the device?use the device
ID or other special information?In which brach of the dirctory tree exist
the drivers?Does a new downloaded device driver need to have a register to
the QNX or just copy it to somewhere?
3,how does the QNX know which process shall be actived?
4,if you want to dial up,you have to tell the dial application the
device(/dev/ser3 or something like that),and the /dev/ser3 is related to a
process of devc-8250,then how about the audio?
ChaoLi <qnx_basic@sohu.com> wrote:
1,who will scan the device?the Neutrino or other manager?
The enumerators at the start do all that work
2,how does the QNX decide which driver shall match the device?use the device
ID or other special information?In which brach of the dirctory tree exist
the drivers?Does a new downloaded device driver need to have a register to
the QNX or just copy it to somewhere?
The shared lib/drivers are in /lib/dll/deva-*
4,if you want to dial up,you have to tell the dial application the
device(/dev/ser3 or something like that),and the /dev/ser3 is related to a
process of devc-8250,then how about the audio?
/dev/snd is the registered namespace, and inside are further controls for
the audio device (such as mixer etc).
-Adam
just another confusion…what’s the process for the /dev/snd just like the
devc-8250 for the /dev/ser3?
-ChaoLi
Thanks.
“Operating System for Tech Supp” <os@qnx.com> wrote in message
news:9o7nkv$el2$3@nntp.qnx.com…
ChaoLi <> qnx_basic@sohu.com> > wrote:
1,who will scan the device?the Neutrino or other manager?The enumerators at the start do all that work
2,how does the QNX decide which driver shall match the device?use the
device
ID or other special information?In which brach of the dirctory tree
exist
the drivers?Does a new downloaded device driver need to have a register
to
the QNX or just copy it to somewhere?The shared lib/drivers are in /lib/dll/deva-*
4,if you want to dial up,you have to tell the dial application the
device(/dev/ser3 or something like that),and the /dev/ser3 is related to
a
process of devc-8250,then how about the audio?/dev/snd is the registered namespace, and inside are further controls for
the audio device (such as mixer etc).-Adam
ChaoLi <qnx_basic@sohu.com> wrote:
just another confusion…what’s the process for the /dev/snd just like the
devc-8250 for the /dev/ser3?
-ChaoLi
Thanks.
The manager for /dev/snd is io-audio.
Barry
“Operating System for Tech Supp” <> os@qnx.com> > wrote in message
news:9o7nkv$el2$> 3@nntp.qnx.com> …
ChaoLi <> qnx_basic@sohu.com> > wrote:
1,who will scan the device?the Neutrino or other manager?The enumerators at the start do all that work
2,how does the QNX decide which driver shall match the device?use the
device
ID or other special information?In which brach of the dirctory tree
exist
the drivers?Does a new downloaded device driver need to have a register
to
the QNX or just copy it to somewhere?The shared lib/drivers are in /lib/dll/deva-*
4,if you want to dial up,you have to tell the dial application the
device(/dev/ser3 or something like that),and the /dev/ser3 is related to
a
process of devc-8250,then how about the audio?/dev/snd is the registered namespace, and inside are further controls for
the audio device (such as mixer etc).-Adam
Thanks very much for your help…
“Operating System for Tech Supp” <os@qnx.com> wrote in message
news:9oa3k9$t1t$1@nntp.qnx.com…
ChaoLi <> qnx_basic@sohu.com> > wrote:
just another confusion…what’s the process for the /dev/snd just like
the
devc-8250 for the /dev/ser3?
-ChaoLi
Thanks.The manager for /dev/snd is io-audio.
Barry
“Operating System for Tech Supp” <> os@qnx.com> > wrote in message
news:9o7nkv$el2$> 3@nntp.qnx.com> …
ChaoLi <> qnx_basic@sohu.com> > wrote:
1,who will scan the device?the Neutrino or other manager?The enumerators at the start do all that work
2,how does the QNX decide which driver shall match the device?use the
device
ID or other special information?In which brach of the dirctory tree
exist
the drivers?Does a new downloaded device driver need to have a
register
to
the QNX or just copy it to somewhere?The shared lib/drivers are in /lib/dll/deva-*
4,if you want to dial up,you have to tell the dial application the
device(/dev/ser3 or something like that),and the /dev/ser3 is related
to
a
process of devc-8250,then how about the audio?/dev/snd is the registered namespace, and inside are further controls
for
the audio device (such as mixer etc).-Adam
\