Hi,
My input in this regard is:
1) The new stack must be detach safe. I.E. no race conditions at detatch.
2) The stack must be able to take an arbitrary mutex, that is provided by the
low level device driver, and not just Giant.
--HPS
___
freebsd-hac
On Mon, Apr 16, 2007 at 05:14:06PM +1000, Alan Garfield wrote:
> Hi all!
>
> A question, is it ok to just say pass an entire rx buffer of your
> ethernet device up the chain and let the ip stack figure out the frame
> size.
>
> I have a device that can only ever receive 255 bytes of data, I recei
> The PR conf/107453 (calendar.judaic is out of date) is still pending. I
> submitted the patch to correct this bug back in January. It is just a
> replacement of an ASCII text file and should not affect the operation of
> the OS. Could some one with the commit bit please look at this and commit
>
On Tue, 2007-04-17 at 21:16 +0400, Yar Tikhiy wrote:
> > In addition to the other advise, you might also look at if_ed.c. It
> > is a little complicated since it talks to real hardware, and that
> > hardware is, ummm, a little icky.
>
> That little thing Alan is writing a driver for should be sim
2007/4/17, Marcel Moolenaar <[EMAIL PROTECTED]>:
Thanks for detailed useful reply.
As for vtc(4): I've not been working on input devices because of the
lack of a generic layer. Note that vtc(4) deals with the low-level
console as much as it deals with user-visible terminals, so from that
point
On Apr 17, 2007, at 3:17 PM, Maxim Zhuravlev wrote:
2007/4/17, Marcel Moolenaar <[EMAIL PROTECTED]>:
Thanks for detailed useful reply.
As for vtc(4): I've not been working on input devices because of the
lack of a generic layer. Note that vtc(4) deals with the low-level
console as much as it
On Apr 17, 2007, at 10:21 AM, thIOretic wrote:
I would like to get info from everyone, who may take similar
efforts in FreeBSD input handling. I'm aware of
* newpsm framework
* KGI/KII
* vtc(4) was mentioned, but its code seems to do nothing from my
project thesis perspective. Or I've mi
Hi, hackers.
I'm working on 'Generic input device layer' GSoC2007 project
(http://wiki.freebsd.org/SummerOfCode2007). This mail is actually to introduce
my ideas and to synchronize it with current community efforts.
--Intro--
The project addresses input devices handling and multiplexing. The
On Mon, Apr 09, 2007 at 10:23:00PM -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Alan Garfield <[EMAIL PROTECTED]> writes:
> : I'd like to port/re-write this driver for FreeBSD but I cannot find
> : enough documentation and examples of a basic Ethernet driver for
> :
In message: <[EMAIL PROTECTED]>
"Daniel O'Connor" <[EMAIL PROTECTED]> writes:
: I am installing FreeBSD 6.2/amd64 on a Supermicro P8SCT however the install
: kernel refuses to attach the floppy (it returns ENOMEM). If I boot the same
: kernel without the mfsroot image it sees it fine
The PR conf/107453 (calendar.judaic is out of date) is still pending. I
submitted the patch to correct this bug back in January. It is just a
replacement of an ASCII text file and should not affect the operation of
the OS. Could some one with the commit bit please look at this and commit
it?
Also
Zhang Weiwu wrote:
On Tue, 2007-04-17 at 10:37 +0300, Nikos Vassiliadis wrote:
On Monday 16 April 2007 21:24, Zhang Weiwu wrote:
Pieter de Goeje 写道:
I think your patch looks good, however there have been some changes to ftpd
since 6.1. Also, since lukemftp is imported from NetBSD, you might
The PR conf/107453 (calendar.judaic is out of date) is still pending. I
submitted the patch to correct this bug back in January. It is just a
replacement of an ASCII text file and should not affect the operation of
the OS. Could some one with the commit bit please look at this and commit
it?
Also
On Tue, 2007-04-17 at 10:37 +0300, Nikos Vassiliadis wrote:
> On Monday 16 April 2007 21:24, Zhang Weiwu wrote:
> > Pieter de Goeje 写道:
> > > I think your patch looks good, however there have been some changes to
> > > ftpd
> > > since 6.1. Also, since lukemftp is imported from NetBSD, you might
I am installing FreeBSD 6.2/amd64 on a Supermicro P8SCT however the install
kernel refuses to attach the floppy (it returns ENOMEM). If I boot the same
kernel without the mfsroot image it sees it fine so.
I am trying to find out more information about what memory is being used,
etc.. Does anyon
15 matches
Mail list logo
