when the driver ioctl (i.e. ifp->if_ioctl) is called with either
SIOCADDMULTI or SIOCDELMULT, NULL value is passed as data argument to the
ioctl function. but going through the code(in net/if.c file if_addmulti
and if_delmulti functions) doesn't reveal the logic behind it. can anyone
tell me why
On Wed, 1 Aug 2001, Eugene L. Vorokov wrote:
> Yet another issue, I have run config -g, then make depend, make and
> make install.debug. But my /kernel is still about 2mb long, which probably
> means it's not really debug kernel. However I see kernel.debug in the
> compile directory which is abo
the device to which i am writing a driver doesn't have a pre-assigned MAC
address. only after the system boots up, a user level program will assign
it a MAC address.
I want to know if it is correct to attach a network interface without MAC
address.
And if it is o.k., when i get the MAC address
interrupts are active, which part of the o.s. code i needs to modify.
considering this is very critical code, i would like to go through some
documentation, is there any thing available?
thanks,
mohan
On Wed, 24 Jan 2001, Mohana Krishna Penumetcha wrote:
> hi,
>
> we are writing a driver(Fr
hi,
we are writing a driver(FreeBSD 4.0) for a switch connected to a PCI port.
the interrupt handling routine is not getting called. we checked the
switch IRQ status register and find some interrupts to be pending. we
have no clue about what is happening, can someone give a few ideas about
what c
On Thu, 11 Jan 2001, Julian Elischer wrote:
> Mohana Krishna Penumetcha wrote:
> >
> > > * Mohana Krishna Penumetcha <[EMAIL PROTECTED]> [010111 03:08] wrote:
> > > >
> > > >
> > > > > Afaik, on i386 you have ~4k of kernel stack, h
> * Mohana Krishna Penumetcha <[EMAIL PROTECTED]> [010111 03:08] wrote:
> >
> >
> > > Afaik, on i386 you have ~4k of kernel stack, however you have to
> > > realize that driver entry can come from an interrupt generated when
> > > the stack i
> Afaik, on i386 you have ~4k of kernel stack, however you have to
> realize that driver entry can come from an interrupt generated when
> the stack is already nearly exhausted. I'm not really that much
> of a driver programmer, but I've heard of people facing this problem
> before, solutions v
we are testing our driver for 4.0 freeBSD. kernel is panicing in the
attach routine with the message "double fault". the longest sequence of
function calls from the attach routine use 180 bytes of kernel stack(this
includes only the local variable), i read in the mailing lists that kernel
stack
hi,
where can i find the sources corresponding to /dev/null??
-Regards
mohan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
hi,
In an ealier mail some one has sent a list of suggested reading for
device drivers(none of them are specific to FreeBSD).
i found unix device drivers by george pajari very useful. the methodology
i followed is to read a chapter from that book and read the FreeBSD
sources for simillar device
hi,
is the PCI Specification avaialable on the web? i tried a couple of search
engines, couldn't find it.
--mohan
Telecom R&D , FAC-D, SAS
ph:- 5281461 x3078
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
hi,
HP-UX device driver reference manual says,
"The side-effects of any write are not guaranteed to happen
immediately. Writes are posted; they will complete eventually"
to make sure all writes are flushed from the queue, it suggests to perform
a read operation.
i would like to know i
hi,
i am planning to develope a freebsd driver for a network adapter card. i
checked the freebsd.org for driver specific information, but couldn't find
any. can someone give pointers to either books or resources on the
internet.
thank you in advance,
mohan
To Unsubscribe: send mail to [EMAIL
14 matches
Mail list logo
