From: Heiko Bauke <heiko.bauke@snafu.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Realtek Ethernet drivers
Date: Mon, 13 Sep 2010 09:59:12 +0200 [thread overview]
Message-ID: <20100913095912.74d7f0f1@tron.localdomain> (raw)
In-Reply-To: <20100912223724.GA15934@electric-eye.fr.zoreil.com>
Dear Francois,
On Mon, 13 Sep 2010 00:37:25 +0200
Francois Romieu <romieu@fr.zoreil.com> wrote:
> It's probably fixed with one of :
> - 81a95f049962ec20a9aed888e676208b206f0f2e /
> 024a07bacf8287a6ddfa83e9d5b951c5e8b4070e
> - 908ba2bfd22253f26fa910cd855e4ccffb1467d0
> - 78f1cd02457252e1ffbc6caa44a17424a45286b8
>
> [...]
> > P.S. I am running 2.6.32-24-generic on a 32-bit Ubuntu 10.04.1 LTS
> > box.
>
> Your 2.6.32-24-generic includes :
> - 908ba2bfd22253f26fa910cd855e4ccffb1467d0
> - 78f1cd02457252e1ffbc6caa44a17424a45286b8
>
> But it misses 81a95f049962ec20a9aed888e676208b206f0f2e and
> 024a07bacf8287a6ddfa83e9d5b951c5e8b4070e
I thank you for your reply. If there is time I will try a more recent
kernel. (For the moment the Realtek drivers are fine for me.) I
know how to (re-)compile distribution kernels and how to compile a
vanilla kernel from kernel.org. However, I have no idea what the
hex-codes you mentioned mean. Can you give me a hint?
Regards,
Heiko
--
-- Die glücklichen Sklaven sind die erbittertsten Feinde der Freiheit.
-- (Marie von Ebner-Eschenbach, öst. Schriftst., 1830-1916)
-- Number Crunch Blog @ http://numbercrunch.de
-- Heiko Bauke @ http://www.mpi-hd.mpg.de/personalhomes/bauke
next prev parent reply other threads:[~2010-09-13 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 19:04 Heiko Bauke
2010-09-12 22:37 ` Francois Romieu
2010-09-13 7:59 ` Heiko Bauke [this message]
2010-09-13 16:14 ` Tim Gardner
2010-09-13 19:22 ` David Miller
2010-09-13 17:41 ` Ben Gamari
2010-09-13 19:01 ` dave b
2010-09-13 19:00 ` Francois Romieu
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=20100913095912.74d7f0f1@tron.localdomain \
--to=heiko.bauke@snafu.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®