[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1398972728.3056.49.camel@LTIRV-MCHAN1.corp.ad.broadcom.com>
Date: Thu, 1 May 2014 12:32:08 -0700
From: Michael Chan <mchan@...adcom.com>
To: "Magnos A. Hammes" <magnos@...hos.com.br>
CC: <netdev@...r.kernel.org>,
"desenvolvimento@...hos.com.br" <desenvolvimento@...hos.com.br>
Subject: Re: [PATCH] drivers/net/ethernet/broadcom/bnx2.c
On Thu, 2014-05-01 at 15:49 -0300, Magnos A. Hammes wrote:
> Yes, I have some udev rules that run at system boot, but the only
> thing
> I do is:
>
> /sbin/udevd --daemon
> /sbin/udevadm trigger --type=subsystems --action=add
> /sbin/udevadm trigger --type=devices --action=add
> /sbin/udevadm settle
>
> Udev runs normally and returns no errors or warnings and dmesg shows
> nothing weird.
>
> So, you think this may be a problem with my udev rules or a udev bug?
>
> I'm using udev version 182.
udev is involved in locating and loading the firmware file. On my
system, I have /lib/udev/firmware.sh and a
generic /lib/udev/rules.d/50-firmware.rules to make request_firmware()
work. Your system may be different.
>
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists