On Thu, 25-Dec-2008 at 13:57:00 +, Rui Paulo wrote:
>
> On 25 Dec 2008, at 09:53, Andre Albsmeier wrote:
>
> > Hello all,
> >
> > I am writing a driver which needs to access memory at a
> > specific location. The location depends on what the BIOS
> > has configured into the host bridge. For e
On 25 Dec 2008, at 09:53, Andre Albsmeier wrote:
Hello all,
I am writing a driver which needs to access memory at a
specific location. The location depends on what the BIOS
has configured into the host bridge. For example, my
current machine uses an Intel 975X chipset and the memory
location I
> hi,
> Thanx Julian for pointing me to the tunnel pseudo-driver.
> But my major concern was regarding linking the driver to the kernel( i
> am trying to use static linking stuff). I am presently doing
> a major grep on "tun" 8-)
> It would be great if i could get some docs regding w
es/* files???
jayesh
>From: Julian Elischer <[EMAIL PROTECTED]>
>To: Brian Somers <[EMAIL PROTECTED]>
>CC: Greg Lehey <[EMAIL PROTECTED]>, Jayesh Krishna
><[EMAIL PROTECTED]>, [EMAIL PROTECTED]
>Subject: Re: Writing device drivers (was: help me please
Brian Somers wrote:
>
> > On Wednesday, 9 May 2001 at 10:40:50 +0530, Jayesh Krishna wrote:
> > > Hi guys...
> > > I am comfortable with Linux Device Drivers. Presently I am trying
> > > to write some pseudo-drivers in FreeBSD(4.2-Release). I tried out
> > > make_pseudo_driver.sh
> > > in the /u
> On Wednesday, 9 May 2001 at 10:40:50 +0530, Jayesh Krishna wrote:
> > Hi guys...
> > I am comfortable with Linux Device Drivers. Presently I am trying
> > to write some pseudo-drivers in FreeBSD(4.2-Release). I tried out
> > make_pseudo_driver.sh
> > in the /usr/share/examples/drivers but it do
On Sun, Dec 17, 2000 at 10:15:44PM -0700, Wes Peters wrote:
> ... Perhaps a good project for someone who wants to under-stand FreeBSD
> device drivers would be to update the section 9 man pages?
Speaking of which, I have a few changes that I wanted to post for man9/
section of the repository. Th
On 19 Dec 2000, Nat Lanza wrote:
> Christopher Nielsen <[EMAIL PROTECTED]> writes:
>
> > Not to be obtuse, but the source always documents the
> > current kernel for any OS...
>
> If you believe that the source is always adequate documentation for
> kernel programming, especially in the Linux w
In message <[EMAIL PROTECTED]>, Nat Lanza writes:
>If you believe that the source is always adequate documentation for
>kernel programming, especially in the Linux world, I have a bridge to
>sell that you might be interested in.
Is it open source? If so, I will be able to adapt it to my own purp
Christopher Nielsen <[EMAIL PROTECTED]> writes:
> Not to be obtuse, but the source always documents the
> current kernel for any OS...
If you believe that the source is always adequate documentation for
kernel programming, especially in the Linux world, I have a bridge to
sell that you might be
Christopher Nielsen wrote:
>
> On 17 Dec 2000, Nat Lanza wrote:
>
> > Nothing documented the current kernel,
>
> Not to be obtuse, but the source always documents the
> current kernel for any OS...
Aww come on man- that was just obtuse.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "un
On Tue, 19 Dec 2000, Christopher Nielsen wrote:
> On 17 Dec 2000, Nat Lanza wrote:
>
> > Nothing documented the current kernel,
>
> Not to be obtuse, but the source always documents the
> current kernel for any OS...
>
Yes, so it must be a real pain to write drivers for a closed-source OS
like W
On 17 Dec 2000, Nat Lanza wrote:
> Nothing documented the current kernel,
Not to be obtuse, but the source always documents the
current kernel for any OS...
--
Christopher Nielsen
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the bod
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Julian Elischer writes:
> : I have the pci/isa driver skeleton pretty up-to-date, but it doesn't
> : have any DMA example code, nor does it have any sample code for
> : pccard or cardbus .
>
> Aren't there two kinds of DMA that we need to wor
Hi guys,
On Mon, 18 Dec 2000, Gregory Sutter wrote:
> On 2000-12-17 22:12 -0700, Wes Peters <[EMAIL PROTECTED]> wrote:
> > Sergey Babkin wrote:
> > > Look at the DaemonNews (www.daemonnews.org), the Blueprints
> > > column. If I remember the months correctly, in the July 2000
> > > issues ther
In message <[EMAIL PROTECTED]> Julian Elischer writes:
: I have the pci/isa driver skeleton pretty up-to-date, but it doesn't
: have any DMA example code, nor does it have any sample code for
: pccard or cardbus .
Aren't there two kinds of DMA that we need to worry about? Those that
are "isadma
Wes Peters wrote:
>
> Devin Butterfield wrote:
> >
> > This is IMHO one of the advantages linux has over FreeBSD. You can run
> > by your local Barnes & Noble bookstore and pick up a copy of "Linux
> > Device Drivers" and start writing code that you actually understand.
>
> And they'll run fine
On 2000-12-17 22:12 -0700, Wes Peters <[EMAIL PROTECTED]> wrote:
> Sergey Babkin wrote:
> > David Preece wrote:
> > > At 13:02 17/12/00 +, you wrote:
> > > >Does anyone have any good tips to get started / HowTo's, or some simple
> > > >examples
> > > >that will give me knowledge like the PC Sp
Sergey Babkin wrote:
>
> David Preece wrote:
> >
> > At 13:02 17/12/00 +, you wrote:
> > >Does anyone have any good tips to get started / HowTo's, or some simple
> > >examples
> > >that will give me knowledge like the PC Speaker or something simple like
> > >that?
> >
> > This is turning into
Devin Butterfield wrote:
>
> This is IMHO one of the advantages linux has over FreeBSD. You can run
> by your local Barnes & Noble bookstore and pick up a copy of "Linux
> Device Drivers" and start writing code that you actually understand.
And they'll run fine in Linux 2.0.43pre11 or something
Devin Butterfield <[EMAIL PROTECTED]> writes:
> This is IMHO one of the advantages linux has over FreeBSD. You can run
> by your local Barnes & Noble bookstore and pick up a copy of "Linux
> Device Drivers" and start writing code that you actually understand.
It's less of an advantage than you m
David Preece wrote:
>
> At 13:02 17/12/00 +, you wrote:
> >Does anyone have any good tips to get started / HowTo's, or some simple
> >examples
> >that will give me knowledge like the PC Speaker or something simple like
> >that?
>
> This is turning into a FAQ, but don't worry about it. The us
David Preece wrote:
>
> At 13:02 17/12/00 +, you wrote:
> >Does anyone have any good tips to get started / HowTo's, or some simple
> >examples
> >that will give me knowledge like the PC Speaker or something simple like
> >that?
>
> This is turning into a FAQ, but don't worry about it. The us
At 13:02 17/12/00 +, you wrote:
>Does anyone have any good tips to get started / HowTo's, or some simple
>examples
>that will give me knowledge like the PC Speaker or something simple like
>that?
This is turning into a FAQ, but don't worry about it. The usual answer is
to take one of the exi
> I ran into this same problem when modifying the vmmon VMWare driver for
> FreeBSD to support mulitple emulator instances. FreeBSD's VFS does not
> have a concept of stateful file access: there are open's and close's, but
> the VOP_READ/WRITE operations are not associated with sessions. This
[.
On Wed, 26 Jul 2000, Isaac Waldron wrote:
> I started working on a port of FreeMWare/plex86 (www.plex86.org) to FreeBSD
> yesterday, and have run into a small problem. The basic idea is that I need
> to write a kernel module that implements some ioctls for a new psuedo-device
> that will eventua
In message <005301bff73b$bf8a3460$[EMAIL PROTECTED]> "Isaac Waldron" writes:
: The issue I'm running into is with the function I'm writing to handle the
: ioctls for the device. For one of the ioctls, the code needs to get some
: data from the file descriptor that was passed to the original call
27 matches
Mail list logo
