I couldn't find a maintainer for uftdi(4), so I sent the patch in
as a PR. It is available here:
http://www.freebsd.org/cgi/query-pr.cgi?pr=67357
It adds support for the Intrepid Control Systems USB based vehicle
bus interfaces.
Earlier, I submited a PR that contains a patch that should be
igno
On Tuesday 16 September 2003 04:47 pm, Mike Durian wrote:
> I'm trying to implement a serial protocol that is timing sensitive.
> I'm noticing things like drains and reads and blocking until the
> next kernel tick. I believe this is due to the lbolt sleeps
> in the tty.c cod
On Wednesday 17 September 2003 12:55 am, Terry Lambert wrote:
>
> You need your process to become a process group leader, and then
> you need the serial port you are interested in to become the
> controlling tty for your process.
I thought daemon(3) and TIOCSCTTY would do the trick, however
after
I'm trying to implement a serial protocol that is timing sensitive.
I'm noticing things like drains and reads and blocking until the
next kernel tick. I believe this is due to the lbolt sleeps
in the tty.c code.
It looks like I can avoid these sleeps if isbackground() returns
false, however I can
On Wednesday 27 August 2003 06:00 pm, Andrew Konstantinov wrote:
>
> I have a problem accessing the printer connected to the box via parallel
> port. Whenever I try to send something to /dev/lpt0, it always responds
> with 'device busy' error message,
Was there any follow-up on this? I've noticed
5 matches
Mail list logo