[openbeos] Re: FW: Re: ioperm
- From: "Jan-Rixt Van Hoye" <janvanhoye@xxxxxxxxxx>
- To: <openbeos@xxxxxxxxxxxxx>
- Date: Sun, 26 Oct 2003 11:43:24 +0100
Yes I've searched all along the net to make it possible, but I didn't find
anything. I know now that it would be better to write a device driver for
the fan and then make a little program that uses this driver. It is not
easy for a newbie, but I'm happy that the community helps.
Thx
JR
-----Oorspronkelijk bericht-----
Van: openbeos-bounce@xxxxxxxxxxxxx
[mailto:openbeos-bounce@xxxxxxxxxxxxx]Namens Michael Phipps
Verzonden: zaterdag 25 oktober 2003 22:19
Aan: openbeos@xxxxxxxxxxxxx
Onderwerp: [openbeos] Re: FW: Re: ioperm
I wouldn't use this route, personally.
There is no promise that this will work beyond R1 (or maybe even in R1, for
that matter). This sort of thing really belongs in a device driver. They are
not all that hard to write for BeOS. If you know how the fan works,
something
simple like this should take less than a day to do.
On 2003-10-24 at 08:59:02 [-0400], Axel Dörfler wrote:
> "Jan-Rixt Van Hoye" <janvanhoye@xxxxxxxxxx> wrote:
> > ok, but is there a header file where I can find these functions?
>
> Have a look at:
> http://wiki.bebits.com/page/UndocumentedSyscalls
>
> (that's what Google returns for read_isa_io() :-))
>
> Bye,
> Axel.
- Follow-Ups:
- [openbeos] Re: FW: Re: ioperm
- From: Axel Dörfler
- References:
- [openbeos] Re: FW: Re: ioperm
- From: Michael Phipps
Other related posts:
- » [openbeos] FW: Re: ioperm
- » [openbeos] Re: FW: Re: ioperm
- » [openbeos] Re: FW: Re: ioperm
- » [openbeos] Re: FW: Re: ioperm
- » [openbeos] Re: FW: Re: ioperm
- » [openbeos] Re: FW: Re: ioperm
- » [openbeos] Re: FW: Re: ioperm
- [openbeos] Re: FW: Re: ioperm
- From: Axel Dörfler
- [openbeos] Re: FW: Re: ioperm
- From: Michael Phipps