From: Fred Ollinger <Fred.Ollinger@seescan.com>
To: Dave Mulder <dmulder@lasx.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Updating NIC drivers in older Yocto
Date: Wed, 14 Oct 2015 16:09:43 +0000 [thread overview]
Message-ID: <1444838892200.77547@seescan.com> (raw)
In-Reply-To: <BLUPR10MB073931FBD2D4D84CF807DEA3D0300@BLUPR10MB0739.namprd10.prod.outlook.com>
I think #2 is a reasonable solution.?
________________________________
From: yocto-bounces@yoctoproject.org <yocto-bounces@yoctoproject.org> on behalf of Dave Mulder <dmulder@lasx.com>
Sent: Tuesday, October 13, 2015 1:30 PM
To: yocto@yoctoproject.org
Subject: [yocto] Updating NIC drivers in older Yocto
I have been using a Sandy Bridge Yocto 1.3 build for a couple years now, on off-the-shelf Intel PC motherboards. I also build an application.
I am now looking into using more recent motherboards. The OS boots just fine, but the new NICs (Intel, Realtek) are not supported by the old 3.4.11 kernel.
What's the best way to support new NICs? I can see three options:
1. New Yocto. I suspect (but would be happy to be wrong) that my application would need to be built against a different sysroot/toolchain, which seems like it would cause backward-compatibility problems (can't run new application on old OS), and I would prefer to not have multiple builds of the application and have to have the host software determine which version is needed (it's an embedded application, and the OS is headless).
2. New kernel, old Yocto. I don't know that this is actually an option, or how new of a kernel can be used in Yocto 1.3. If this is an option, it seems like my application would not need to be rebuilt.
3. Loadable drivers for new NICs (rather than using the ones built into the kernel). I don't know that this is doable either.
Are there other options? Can a new application be built that will work with multiple versions of the OS? Is that even a problem, or am I just assuming the worst?
Thanks!
Dave
next prev parent reply other threads:[~2015-10-14 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 20:30 Updating NIC drivers in older Yocto Dave Mulder
2015-10-14 16:09 ` Fred Ollinger [this message]
2015-10-16 16:02 ` Dave Mulder
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=1444838892200.77547@seescan.com \
--to=fred.ollinger@seescan.com \
--cc=dmulder@lasx.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.