From: Arend van Spriel <arend@broadcom.com>
To: Renato <renatoriolino@gmail.com>
Cc: <backports@vger.kernel.org>
Subject: Re: compat-drivers-3.8.3-2-snpu with kernel 2.6.24
Date: Fri, 31 Oct 2014 20:03:16 +0100 [thread overview]
Message-ID: <5453DCF4.9040101@broadcom.com> (raw)
In-Reply-To: <CAG_2TMdYXqO5bRC7gmjY-yZzw-KJQDc2bzsGKj6cdygYPGW1Jw@mail.gmail.com>
On 10/31/14 19:40, Renato wrote:
> Hi,
>
> I have and old Linux system built from scratch based on kernel 2.6.24
> and I need to add support on it for an Atheros ethernet card that
> doesnt have driver for kernel 2.6.24.
>
> Unfortunately we can't update the kernel because my client has a
> control hardware that only have binary e propertery driver for 2.6.24.
>
> Because of that, I'm trying to use compat-drivers to do that.
>
> What I did so far was:
>
> Downloaded compat-drivers-3.8.3-2-snpu and extraceted it.
> Compiled it using:
>
> ./scripts/driver-select alx
> make
> make install
>
> After rebooting, I loaded the compat driver with:
>
> modprobe compat
>
> I can see the following on dmesg:
>
> Compat-drivers backport release: compat-drivers-v3.8.3-2-snpu
> Backport based on linux-stable.git v3.8.3
> compat.git: linux-stable.git
>
> Nothing more. And no eth yet.
>
> What I am missing?
After loading compat you have the glue layer in place to load the actual
3.8.3 drivers on 2.6.24. So your next step would be to modprobe the alx
driver or whatever it is called.
Regards,
Arend
> Thanks
> --
> To unsubscribe from this list: send the line "unsubscribe backports" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-10-31 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 18:40 compat-drivers-3.8.3-2-snpu with kernel 2.6.24 Renato
2014-10-31 19:03 ` Arend van Spriel [this message]
[not found] ` <CAG_2TMdhykKiZDKLNVxcYkcZRXTQON6tAZ2SMdf0c4JgAk+Rgg@mail.gmail.com>
2014-10-31 19:26 ` Arend van Spriel
2014-11-03 12:21 ` Renato
2014-11-03 12:37 ` Arend van Spriel
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=5453DCF4.9040101@broadcom.com \
--to=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=renatoriolino@gmail.com \
/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