Yony Yossef wrote:
Thanks for the explanation.
So there's no way to determine this in advance..
What do you mean by 'in advance'? Assuming a fixed hardware
configuration, when the kernel is loaded, you know all the
interface names and can rename them, i.e., in rc.local.
From
Yony Yossef wrote:
Thanks for the explanation.
So there's no way to determine this in advance..
I must build a script that contains my own mapping between MAC
addresses and the wanted interface names and run it after
each driver
load, rename the interfaces if necessary.
you
-Original Message-
From: rea-f...@codelabs.ru [mailto:rea-f...@codelabs.ru]
Sent: Thursday, January 15, 2009 12:01 PM
To: Yony Yossef
Cc: 'Julian Elischer'; Liran Liss; freebsd-...@freebsd.org;
Oleg Kats; 'H.fazaeli'; Eitan Shefi; freebsd-questions@freebsd.org
Subject: Re
Thu, Jan 15, 2009 at 01:15:53PM +0200, Yony Yossef wrote:
You're using your own driver, aren't you? If yes, could you show
your device_method_t structure and the corresponding identify,
probe, attach and detach routines? You're setting the
unit numbers
via 'if_initname(ifp
Eygene Ryabinkin wrote:
...
I wanted to stress only one point: simple 'kldunload driver' and
'kldload driver' makes devices to flip for Yony's case.
This means
that unless some PCI hotplug stuff is here (which I don't
believe to
be present, because no physical cards are touched and
Hi,
I would like to determine the unit number of my network cards, e.g.
make the device on pci0:16 be assigned every time with unit number 0
and pci0:19 with unit number 1.
Is it done by /boot/device.hints?
if so, how?
My cards are:
mtn...@pci0:19:0:0: class=0x02 card=0x001715b3
-Original Message-
From: H.fazaeli [mailto:faza...@sepehrs.com]
Sent: Wednesday, January 14, 2009 6:24 PM
To: Yony Yossef
Cc: freebsd-...@freebsd.org; freebsd-questions@freebsd.org;
Eitan Shefi; Oleg Kats; Liran Liss
Subject: Re: howto determine network device unit number
it?
Yony
Yony Yossef wrote:
Hi,
I would like to determine the unit number of my network cards, e.g.
make the device on pci0:16 be assigned every time with unit
number 0
and pci0:19 with unit number 1.
Is it done by /boot/device.hints?
if so, how?
My cards are:
mtn
Hi,
I would like to determine the unit number of my network cards, make the
device on pci0:16 appear always as mtnic0 and pci0:9 appear always as
mtnic1.
# pciconf -l | grep mtnic
mtn...@pci0:19:0:0: class=0x02 card=0x001715b3 chip=0x636815b3
rev=0xa0 hdr=0x00
mtn...@pci0:16:0:0:
Hi All,
I'm trying to find out whether my ethernet driver is leaking.
I just found out about netstat -m, but I don't understand some of it's
output.
Can somebody explain me what is mbuf+clusters out of packet secondary zone
in use ?
My output shows it raised significantly during equilibrium
Hi All,
What mechanism should I use for making my netwrok driver call a
function every half a second, for instnace?
I am already using task queues but I haven't found a way to make it
work with a timer.
Thanks
Yony
___
freebsd-questions@freebsd.org
Hi,
I'm running cvsup -g -L 2 cvs-supfile with all kinds of host names
from this list:
http://www.freebsd.org/doc/handbook/cvsup.html#HANDBOOK-MIRRORS-CHAPTER-SGML-MIRRORS-IL-CVSUP
I get a Connection refused error.
Help..
Yony
___
Hi All,
I would like to enable my NIC HW VLAN filtering, is there any way for my
driver to access the OS vlan table? (something like vlan_group_get_device on
linux)
I understood from previous investigation that on FreeBSD 6.3 and 7.0 there's
no ioctl informing the driver of vlan
I would like to enable my NIC HW VLAN filtering, is there any way for
my
driver to access the OS vlan table? (something like vlan_group_get_device
on
linux)
I understood from previous investigation that on FreeBSD 6.3 and 7.0
there's
no ioctl informing the driver of vlan
make doesn't know how to make KERNCONF
the command i run is:
cd /usr/src
make buildkernel KERNCONF=MIO
where MIO is my kernel configuration file, living at /usr/src/sys/i386/conf
Are you sure your conf file shouldn't be in /usr/src/sys/amd64/conf ?
YY
Hi,
I have two questions about VLANs on FreeBSD 6.3/7.0.
1.
I'm trying to understand whether HW VLAN filtering can be supported.
Looking at the code I can't find a proper ioctl that will inform the driver
about a vlan creation/destruction.
Is there a way of doing it?
2.
Second issue - is there
working on the regular interface. but
it seems like vlan interfaces does not inherit the parent device
capabilities.
Jack
On Tue, Oct 28, 2008 at 7:43 AM, Yony Yossef [EMAIL PROTECTED]wrote:
Hi,
I have two questions about VLANs on FreeBSD 6.3/7.0.
1.
I'm trying to understand whether
Hi All,
I'm trying to manually build an mbuf chain with clusters in various sizes.
I'm doing it using the MGETHDR and MEXTADD macros, it works fine.
Now I'm looking for the simplest way to free an mbuf cluster, since I want
to free the clusters seperately. This function will be given as a
Hi All
I'm working on an Ethernet driver for FreeBSD 7.0.
Taking network performance numbers I encountered very long mbuf chains on
the sender side.
The symptom is constant, always during iperf/netperf TCP stream tests with
message sizes of 128 bytes (200 mbufs per chain),
1024 bytes (30-60
Hi,
I would really like to use valgrind on my FreeBSD machine, but.. :-)
-Yony
make
=== Building for valgrind-352_7
gmake all-recursive
gmake[1]: Entering directory
`/usr/ports/devel/valgrind/work/valgrind-stable-352'
Making all in include
gmake[2]: Entering directory
Hi all,
I'm looking for methods to debug a kernel process memory overrun.
I'm working on an Ethernet driver for FreeBSD 7.0 and I'm facing a crash
after several (kldload + kldunload)s.
The exception is being thrown by the shell process after the last kldunload
successfully ends so I'm guessing
Hi,
After a successful installation, first boot of FreeBSD7 fails upon shell
loading:
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/amd64/reloc.c:341
pid 78 (sh), uid 0: exited on signal 6
I get a prompt asking to provide a shell path. the same error occurs for all
existing shells (sh,
Hi Kris,
Please see below
Hi all.
I'm trying to debug a spinlock held too long error.
Therefore I thought compiling my kernel with options WITNESS would be a
good idea.
Using the WITNESS kernel I cannot load my driver with any MTX_SPIN mutex.
I had to change it all to MTX_DEF since
Something is still unclear. All my locks are MTX_DEF type, which means
sleepable, including the one specified in the crash report (MTNIC state
semaphore).
This crash happens when I try to call bus_resource_alloc_any for a SYS_REQ
which is trying to obtain the second lock (ACPI root bus).
Problem solved :-)
Thank you very much for your patience Kris..
On Tue, Jul 15, 2008 at 5:14 PM, Kris Kennaway [EMAIL PROTECTED] wrote:
Yony Yossef wrote:
Something is still unclear. All my locks are MTX_DEF type, which
means
sleepable, including the one specified
Hi all.
I'm trying to debug a spinlock held too long error.
Therefore I thought compiling my kernel with options WITNESS would be a
good idea.
Using the WITNESS kernel I cannot load my driver with any MTX_SPIN mutex.
I had to change it all to MTX_DEF since every MTX_SPIN got me this error:
Hi All,
I'm trying to find the equivilents for Linux's schedule() and
set_task_state(TASK_RUNNING).
Does anybody have a tip?
Thanks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
27 matches
Mail list logo
