Hi,
Geert Uytterhoeven wrote:
You didn't mmap() /dev/mem? You do need to use the mmap() result as _IO_BASE,
not the physical 0xfe00.
That's what you can do in ioperm().
Thanks for that! I got your program to build, and mine to build (and
work as I expected) after using mmap() from you
On Tue, 4 Feb 2003, Ross Vumbaca wrote:
> Geert Uytterhoeven wrote:
> >>O.k the inb and outb is fine now, but I get this weird (link) problem:
>
> >>/sio.c:46: undefined reference to `local symbols in discarded section
> >>.fixup'
> >>/sio.c:46: undefined reference to `local symbols in discarded
Hi,
Geert Uytterhoeven wrote:
O.k the inb and outb is fine now, but I get this weird (link) problem:
/sio.c:46: undefined reference to `local symbols in discarded section
.fixup'
/sio.c:46: undefined reference to `local symbols in discarded section
.fixup'
/sio.c:46: undefined reference to
On Tue, 4 Feb 2003, Ross Vumbaca wrote:
> Geert Uytterhoeven wrote:
> >>I tried to built it (after changing CHRP_ISA_IO_BASE), but for some
> >>reason there is no "inb" or "outb" functions, i.e
> >>
> >>sio.c: In function `sio_write':
> >>sio.c:80: warning: implicit declaration of function `outb'
Hi,
Geert Uytterhoeven wrote:
I tried to built it (after changing CHRP_ISA_IO_BASE), but for some
reason there is no "inb" or "outb" functions, i.e
sio.c: In function `sio_write':
sio.c:80: warning: implicit declaration of function `outb'
sio.c: In function `sio_read':
sio.c:87: warning: impl
On Tue, 4 Feb 2003, Ross Vumbaca wrote:
> Geert Uytterhoeven wrote:
> > ISA I/O space is the low part of PCI I/O space.
> > ISA memory space is something different (not available on Macs).
>
> I should mention I am not using a Mac, it is an "AmigaOne/MAI Teron"
> board, which is basically an ATX
Hi,
Geert Uytterhoeven wrote:
ISA I/O space is the low part of PCI I/O space.
ISA memory space is something different (not available on Macs).
I should mention I am not using a Mac, it is an "AmigaOne/MAI Teron"
board, which is basically an ATX board with a VIA Southbridge (hence the
ISA pe
On Tue, 4 Feb 2003, Ross Vumbaca wrote:
> Geert Uytterhoeven wrote:
> > On Mon, 3 Feb 2003, vinai wrote:
> >
> >>I'm not anywhere near an expert on this, so take what I say with a pound
> >>of salt or so ... :) I was reading up on the PCI specifications to try
> >>to understand a little bit about
Hi,
Geert Uytterhoeven wrote:
On Mon, 3 Feb 2003, vinai wrote:
I'm not anywhere near an expert on this, so take what I say with a pound
of salt or so ... :) I was reading up on the PCI specifications to try
to understand a little bit about drivers, and it was mentioned that the
x86 architectu
On Mon, 3 Feb 2003, vinai wrote:
> I'm not anywhere near an expert on this, so take what I say with a pound
> of salt or so ... :) I was reading up on the PCI specifications to try
> to understand a little bit about drivers, and it was mentioned that the
> x86 architecture use I/O space to access
Hi,
I'm not anywhere near an expert on this, so take what I say with a pound
of salt or so ... :) I was reading up on the PCI specifications to try
to understand a little bit about drivers, and it was mentioned that the
x86 architecture use I/O space to access devices, whereas with PowerPC
system
Hi,
I'm was trying to "debug" a problem with a driver and my PowerPC board,
and I wrote this simple program which works fine on an x86 Debian Woody
box (and does not use x86 dependent functions as far as I can tell):
#include
#include
int main() {
ioperm(0x00, 0xff, 1);
pri
12 matches
Mail list logo
