From: Greg KH <gregkh@linuxfoundation.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev not renaming interface if driver is built-in
Date: Wed, 03 Dec 2014 05:13:34 +0000 [thread overview]
Message-ID: <20141203051334.GA7382@kroah.com> (raw)
In-Reply-To: <CAOi_9k_LXDGZsc18AS7epxW4eUkCX5Hy1hA9Gj2-gQ-gAVoU5Q@mail.gmail.com>
On Wed, Dec 03, 2014 at 10:16:49AM +0530, Rajib Karmakar wrote:
> On Tue, Dec 2, 2014 at 8:51 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Tue, Dec 02, 2014 at 07:16:19PM +0530, Rajib Karmakar wrote:
> >> Hello,
> >>
> >> My ethernet driver was built as a module and once it was probed, I can
> >> see that udev renames the interface. but when I try to have the
> >> ethernet driver as built-in. the driver is probed but udev no longer
> >> renames the interface.
> >>
> >> Can you please help me in this?
> >
> > You aren't providing the version of udev you are using, the distro you
> > are using, what initramfs you are using, or the kernel you are using, so
> > it's a bit hard to help you out without that...
> >
> > thanks,
> >
> > greg k-h
> Sorry for this, I am a bit new to kernel driver development and does
> not quite understand a lot of things. Here are the details you wanted,
>
> kernel version: 2.6.34
Wow that's a very old and obsolete and unsupported kernel version, you
really are on your own here. If you have to use this kernel, get
support from the company that is forcing you to stick with it, that is
what you are paying them for.
Best of luck,
greg k-h
prev parent reply other threads:[~2014-12-03 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 13:58 udev not renaming interface if driver is built-in Rajib Karmakar
2014-12-02 15:21 ` Greg KH
2014-12-03 4:58 ` Rajib Karmakar
2014-12-03 5:13 ` Greg KH [this message]
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=20141203051334.GA7382@kroah.com \
--to=gregkh@linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).