> I think that could work (only an idea, not tested):
>
>
> struct Region
> {
> void * p;
> size_t s;
> };
>
>
> #define IOBIG _IOWR ('b', 123, struct Region)
>
>
> userland:
>
> char data[1000];
> struct Region r;
>
> r.p = data;
> r.s = sizeof data;
> int error = ioctl (fd,
Hello everyone,
Over the last 2 weeks, I have been working on a port of FreeBSD for the
XBox. During this effort, Ed Schouten has given me assistance by
reviewing patches and giving advice.
The port is fully functional. The framebuffer is fully supported, same goes
for sound and USB devices (such
Hello.
The functions await() and asleep() in kern_synch.c
are marked as EXPERIMENTAL/UNTESTED.
Is this comment still valid? Does anyone have used
those functions successfully? Should I better not
use them in my device driver code for RELENG_4?
How do I correctly cancel a request (as I should do
ac
> I just had a lengthy discussion with a couple of guys about the 802.11
> protocol. One had said that the random delays inserted before
> transmission was one of the *IFS delays (can't remember which
> now), and that it was a standard 802.11 number, not a random
> delay.
Yep - in 802.11b CWmin
Felix-KM wrote:
I think that could work (only an idea, not tested):
struct Region
{
void * p;
size_t s;
};
#define IOBIG _IOWR ('b', 123, struct Region)
userland:
char data[1000];
struct Region r;
r.p = data;
r.s = sizeof data;
int error = ioctl (fd, IOBIG, &r);
kernel:
int my_i
Norbert Koch wrote:
Hello.
The functions await() and asleep() in kern_synch.c
are marked as EXPERIMENTAL/UNTESTED.
Is this comment still valid? Does anyone have used
those functions successfully? Should I better not
use them in my device driver code for RELENG_4?
How do I correctly cancel a requ
David Malone wrote:
I just had a lengthy discussion with a couple of guys about the 802.11
protocol. One had said that the random delays inserted before
transmission was one of the *IFS delays (can't remember which
now), and that it was a standard 802.11 number, not a random
delay.
Yep - in
Adding -ftracer to my make.conf causes problems with
/src/sbin/shutdown/shutdown.c
This is my make.conf settings
CPUTYPE=athlon-xp
CFLAGS=-O2 -pipe -ffast-math -funroll-loops -ftracer
COPTFLAGES=-O2 -pipe -funroll-loops -ffast-math -ftracer
Doing a little research I found these items:
-ftrace
On Tue, Jul 05, 2005 at 05:39:33PM +0200, Jeremie Le Hen wrote:
> Hi hackers,
>
> I'm still working on integrating the ProPolice patch in FreeBSD CURRENT.
> A small reminder :
> The ProPolice patch prevents from stack-based buffer overflows
> but setting a canary between character arra
On Wed, Jul 27, 2005 at 01:26:45AM +0200, Jeremie Le Hen wrote:
> Being full of enthusiasm, I checked if by chance libraries could have
> dynamic object dependencies. It appears this is not the case, but
> since I'm neither a GCC nor binutils hacker, maybe there is a way to
> achieve this. This i
In message: <[EMAIL PROTECTED]>
Rink Springer <[EMAIL PROTECTED]> writes:
: Over the last 2 weeks, I have been working on a port of FreeBSD for the
: XBox. During this effort, Ed Schouten has given me assistance by
: reviewing patches and giving advice.
Way Cool!
Warner
__
> > The functions await() and asleep() in kern_synch.c
> > are marked as EXPERIMENTAL/UNTESTED.
> > Is this comment still valid? Does anyone have used
> > those functions successfully? Should I better not
> > use them in my device driver code for RELENG_4?
> > How do I correctly cancel a request (a
12 matches
Mail list logo
