Hello,
On Thu, 3 May 2001, sébastien person wrote:
> I think that use of pipe isn't preconised because I must fork process
> to use pipe, I search something like ioctl but in the other way :
>
> kernel process ---> user process
What about using /proc/ ?
Gruß,
Markus
--
| Gluecklich ist, wer
sébastien person wrote:
>
> Le Thu, 3 May 2001 08:46:05 -0400 (EDT)
> Mark Hahn <[EMAIL PROTECTED]> à écrit :
>
> > > I think that use of pipe isn't preconised because I must fork process
> > > to use pipe,
> >
> > I guess you mean "because a user-level process would block on the pipe".
> > and
a) just make your management app periodically issue
ioctl(fd, GET_CONFIG_INFO, ...)
and make the driver return -1 when the info is not present
b) make a new device and open it with management app
c) make a new node in /proc and open it with management app
(cons: requires /proc to be
Le Thu, 3 May 2001 08:46:05 -0400 (EDT)
Mark Hahn <[EMAIL PROTECTED]> à écrit :
> > I think that use of pipe isn't preconised because I must fork process
> > to use pipe,
>
> I guess you mean "because a user-level process would block on the pipe".
> and you don't want to block. the alternative
On Thursday 03 May 2001 14:29, sébastien person wrote:
> hi,
>
> I've made a network driver wich is attached to the serial port.
> The network hardware is able to return information to the pc. theses
> informations are belong to the configuration of the hardware. I
yes yes all your base are
hi,
I've made a network driver wich is attached to the serial port.
The network hardware is able to return information to the pc. theses
informations are belong to the configuration of the hardware. I
succeed on receive information in the driver but I've no idea to alert
higher process (like
hi,
I've made a network driver wich is attached to the serial port.
The network hardware is able to return information to the pc. theses
informations are belong to the configuration of the hardware. I
succeed on receive information in the driver but I've no idea to alert
higher process (like
On Thursday 03 May 2001 14:29, sébastien person wrote:
hi,
I've made a network driver wich is attached to the serial port.
The network hardware is able to return information to the pc. theses
informations are belong to the configuration of the hardware. I
yes yes all your base are belong to
Le Thu, 3 May 2001 08:46:05 -0400 (EDT)
Mark Hahn [EMAIL PROTECTED] à écrit :
I think that use of pipe isn't preconised because I must fork process
to use pipe,
I guess you mean because a user-level process would block on the pipe.
and you don't want to block. the alternative is to use
a) just make your management app periodically issue
ioctl(fd, GET_CONFIG_INFO, ...)
and make the driver return -1 when the info is not present
b) make a new device and open it with management app
c) make a new node in /proc and open it with management app
(cons: requires /proc to be
sébastien person wrote:
Le Thu, 3 May 2001 08:46:05 -0400 (EDT)
Mark Hahn [EMAIL PROTECTED] à écrit :
I think that use of pipe isn't preconised because I must fork process
to use pipe,
I guess you mean because a user-level process would block on the pipe.
and you don't want to
Hello,
On Thu, 3 May 2001, sébastien person wrote:
I think that use of pipe isn't preconised because I must fork process
to use pipe, I search something like ioctl but in the other way :
kernel process --- user process
What about using /proc/ ?
Gruß,
Markus
--
| Gluecklich ist, wer
12 matches
Mail list logo
