From: Matt Domsch <Matt_Domsch@Dell.com>
To: linux-hotplug@vger.kernel.org, netdev@vger.kernel.org, "K,
Narendra" <Narendra_K@Dell.com>,
"Hargrave, Jordan" <Jordan_Hargrave@Dell.com>,
"Rose, Charles" <Charles_Rose@Dell.com>,
Co
Subject: biosdevname v0.3.7
Date: Thu, 17 Feb 2011 16:15:40 +0000 [thread overview]
Message-ID: <20110217161540.GA29554@auslistsprd01.us.dell.com> (raw)
biosdevname, now version 0.3.7.
Major visible changes include no longer using '#' in device names (by
popular demand), no longer suggesting new names if running inside a VM
guest (tested with KVM, SLES 10 Xen, XenServer, VMware ESX, but it
uses the generic cpuid test, so should work on most virt platforms),
and a new kernel command line option 'biosdevname={0|1}' which udev
honors, to force enabling or disabling of invoking biosdevname.
Still to come: NPAR partition->port mapping support (initially
Dell-specific, but if NIC vendors have other ways to expose this,
please let me know).
Grab it here:
http://linux.dell.com/files/biosdevname/permalink/biosdevname-0.3.7.tar.gz
http://linux.dell.com/files/biosdevname/permalink/biosdevname-0.3.7.tar.gz.sign
git://linux.dell.com/biosdevname.git
I built this today for Fedora rawhide and F15, and I encourage
other distributions to pick it up as well.
shortlog:
Andrew Cooper (3):
Fix segfault when BIOS advertises zero sized PIRQ Routing Table
Add 'bonding' and 'openvswitch' to the virtual devices list
Typo fixes
Harald Hoyer (1):
Add kernel command line parameter "biosdevname={0|1}" to turn off/on
Matt Domsch (7):
don't build or package dump_pirq, use biosdecode from dmidecode instead
don't use '#' in names, use 'p' instead, by popular demand
properly look for SMBIOS, then $PIR, then recurse
update changelog
Fix test for PIRQ table version
fail PIRQ lookups if device domain is not 0
exit(4) if running a virtual machine
Thanks,
Matt
--
Matt Domsch
Technology Strategist
Dell | Office of the CTO
reply other threads:[~2011-02-17 16:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110217161540.GA29554@auslistsprd01.us.dell.com \
--to=matt_domsch@dell.com \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox