Ok, this has gone on long enough that my normal inhibitions about
driving down the signal-to-noise ratio of a technical list have
long subsided.
Folks, cron is a *LOW LEVEL SERVICE* much in the same vein as UDP.
Neither one makes strong guarantees about ordering, duplication,
or dropped events.
All,
I'm trying to mmap() a region of device memory into user space.
When the user app tries to write to the page, I'm getting a SIGBUS.
My code in foo_mmap() looks essentially like:
...
voff = bhandle + client_offset;
poff = vtophys(voff);
return i386_btop(poff)
All,
Never mind, problem found. A logic bug was preventing me from
setting PROT_READ which was necessary even though these are
write-only registers.
Thanks,
-JohnG
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
All,
I'm doing hardware bringup and am suspecting that our adapter is
dma-ing to the wrong physical address. We know we're getting a PCI
bus transaction when we expect it, but we don't know where it's going.
Until the bus analyzer arrives, what's the easiest way to go through
physical memory lo
> What would you guys do in this case? :)
I'd call up my friendly regional SGI, Sun, IBM, and Compaq reps
and have them put together proposals. I'm a former SGI guy and
know that we've had a bunch of installations of this size and larger
(much larger). It's not that big a deal any more. I don'
> I am trying to find out where the function socket() is actually defined.
sys/kern/uipc_syscalls.c
cscope is your friend.
> Moreover is see __P with all the function prototypes. Can anyone
> tell me what do they mean. I am right now assuming for my work that
> they just mean blank.
Bad assump
Random idea from the peanut gallery...
Find someone who is NDA'd and knows both the programming manual and the
needs of the device driver. Have that person compose a list of those bits
of the manual most necessary for getting a working driver. This would
be an explicit list of figures, diagrams
Lord Isildur wrote:
>
> sine one knows the size of the struct, who need the pointer? just
> take the displacement.
>
> char* buf; /* some buffer */
> struct foo{
> int header;
> struct funkystruct blah;
> };
>
> (struct foo*)buf; /*your headers are here */
> (struct foo*)buf+1; /* and your data
8 matches
Mail list logo
