linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: firmware hotpluging
Date: Fri, 13 Apr 2007 16:31:37 +0000	[thread overview]
Message-ID: <1176481897.4206.21.camel@lov.localdomain> (raw)
In-Reply-To: <461F31E8.5090802@gmail.com>

On Fri, 2007-04-13 at 12:07 -0400, Dave Sampson wrote:
> The bellow output is what udev monitor --env spits back when I plug in 
> my PCMCIA card (which essentialy loads the module at the same time). I 
> really need to learn more about udev, cause it is a big black box.

You get this event:
  UEVENT[1176480087.807781] add@/class/firmware/0000:02:00.0
  ACTION­d
  DEVPATH=/class/firmware/0000:02:00.0
  SUBSYSTEM=firmware
  SEQNUM\x1037
  FIRMWARE=tiacx100c0D

Do you have that file on your box?:
  /lib/firmware/tiacx100c0D

> Furthermore I don't wish to complicate matters but I notice that it 
> creates device wlan0.. is there a way to make it create a ethX device. I 
> know its a wireless device so that is convention, but the application i 
> am trying to get going (kismet) thinks that acx will mount as a 
> /dev/ethx. If its an easy answer great, if not then lets focus on the 
> firmware first.

Most distros create persistent network names, by writing rules for every
discovered device and assing the same name after reboot. You would just
need to edit the rules file and set a different name.

Kay


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2007-04-13 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13  7:31 firmware hotpluging Dave Sampson
2007-04-13  9:44 ` Kay Sievers
2007-04-13 16:07 ` Dave Sampson
2007-04-13 16:31 ` Kay Sievers [this message]
2007-04-13 17:14 ` Dave Sampson

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=1176481897.4206.21.camel@lov.localdomain \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).