From owner-freebsd-questions@FreeBSD.ORG Thu Jan 15 18:37:43 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF9DB1065676; Thu, 15 Jan 2009 18:37:43 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) by mx1.freebsd.org (Postfix) with ESMTP id 9398F8FC1C; Thu, 15 Jan 2009 18:37:43 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.3/8.14.3) with ESMTP id n0FICBK3081334; Thu, 15 Jan 2009 12:12:11 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.3/8.14.3/Submit) id n0FICBV2081333; Thu, 15 Jan 2009 12:12:11 -0600 (CST) (envelope-from brooks) Date: Thu, 15 Jan 2009 12:12:11 -0600 From: Brooks Davis To: Yony Yossef Message-ID: <20090115181211.GA81115@lor.one-eyed-alien.net> References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496F34D2.7050605@FreeBSD.org> <496F4FD1.4080602@FreeBSD.org> <+b/MqS4l8z9bOD9y4AZP70mtFL0@kjaK+/sQ5DW5981v71UogZJPf/0> <496F7618.8050809@FreeBSD.org> <20def4870901151007s643f6910h1f6dca058852e4b1@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline In-Reply-To: <20def4870901151007s643f6910h1f6dca058852e4b1@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Thu, 15 Jan 2009 12:12:12 -0600 (CST) X-Mailman-Approved-At: Thu, 15 Jan 2009 18:50:07 +0000 Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "H.fazaeli" , rea-fbsd@codelabs.ru, Eitan Shefi , "Bruce M. Simpson" , freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 18:37:44 -0000 --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 15, 2009 at 08:07:35PM +0200, Yony Yossef wrote: > > Eygene Ryabinkin wrote: > > > ... > > > I wanted to stress only one point: simple 'kldunload ' and > > > 'kldload ' 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 there is > > > actually a small amount of PCI hotplug support in FreeBSD), no > > > physical PCI devices get added or removed from the PCI > > child tree. It > > > looks like that something goes wrong during the PCI tree reprobe on > > > the driver module loading. > > > > > > > BTW: Thanks for looking further at the software layer first. > > > > VIM is a wee bit easier to use than a bus analyzer. > > > > Most motherboards don't support PCI geographical addressing, > > so... I wager it's the network driver code which may be the > > source of the problem, based on your analysis! > > > > If this code just doing a blind bump of an instance count and > > using that as a "unit number"... well, that's OK and expected > > for software virtual devices, but is counter-intuitive for > > something like hardware. > > > > But I don't have any mtnic source, so this is pure > > speculation on my part. > > > > > Correct me if I am wrong, but pci_driver_added from /sys/pci/pci.c > > > will invoke device_get_children() to get the list of the attached > > > devices, and for PCI case the list should be static. > > > > > > > Yup, that's right. > > > > > I guess that when Yony will enable verbose boot and will show us > > > kernel messages from two successive kldunload/kldload sequences, we > > > will get some additional information about what's going on. > > > > > > > Hopefully he will chime in... > > > > [bms does some google searching *before* he thinks about > > throwing his toys out of the pram at the Orignal.Poster.] > > > > ding :-) [a light bulb above bms' head] > > > > So... Yony. you're writing a driver. > > Maybe there's a bug in it? > > That's cool, dude. > > Hope it's a nice card and you plan on sharing the sweets with > > the rest of the class. ;-) > > > > But seriously, please mention that you are writing a driver > > in general questions you might ask about the whole system, > > otherwise, FreeBSD volunteers will run around going "Is core > > code broken?" and that's not so good for community stress > > levels as a whole. > > > > with lemonade, > > BMS >=20 > Sorry for risking the whole community with a massive heart attack Bruce :) > Yes, I am writing a driver and yes, it still has a bug or two I guess.. > About sharing it with the rest of the class, that's something I wanted > to ask you guys: what's the procedure for a 10GigE driver to apply > for the FreeBSD kernel? Pretty much just get it working, make sure it's licensed under a BSD, MIT, or ISC license (ideally, others are possible, but require more approval), and then find someone to review and commit it or sponsor the maintainer for a commit bit. =20 > Mellanox has started porting it's products to FreeBSD about a year > ago, hoping to see our 10GigE and InfiniBand drivers inbox next year. Excellent. -- Brooks >=20 > Yony > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >=20 --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFJb3x6XY6L6fI4GtQRAgLWAJwO108Llz3MltWJZ6PT8sa51g007QCfXvsB KaBJchcgQVnEQijFHWhcrnE= =y5TT -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI--