From owner-freebsd-hackers Thu Apr 16 11:42:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05547 for freebsd-hackers-outgoing; Thu, 16 Apr 1998 11:42:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05513 for ; Thu, 16 Apr 1998 18:42:13 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00640; Thu, 16 Apr 1998 11:38:46 -0700 (PDT) Message-Id: <199804161838.LAA00640@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Karl Pielorz cc: hackers@FreeBSD.ORG Subject: Re: Memory mapping via Syscons? In-reply-to: Your message of "Thu, 16 Apr 1998 19:33:07 BST." <35364EE3.2043BF4A@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Apr 1998 11:38:46 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've read somewhere that you can use syscons to map IO memory into > 'userland'? Is this possible? Yes. > I have a simple ISA card that maps in at 0x240 - 0x24F - which I'd like to > read and write to without going through creating a kernel device driver > etc... That's not memory, that's I/O space. Open /dev/io and then use the functions in to perform I/O. > A device driver will probably follow - but if I can just get to the card I > can use a heap of existing code I've allready got to drive it - and worry > about the driver when I have more time... We built a commercial product using user-mode I/O that managed well over 1M/sec using that interface. For many applications, there's no need to do anything more complex. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message