From: Gregoire Favre <Gregoire.Favre@gmail.com>
To: linux-dvb@linuxtv.org, linux-kernel@vger.kernel.org
Cc: ak@suse.de
Subject: Re: BUG : 2.6.21.1 -> 2.6.21.3 breaks cx88 (4 Gb)
Date: Mon, 28 May 2007 11:11:18 +0200 [thread overview]
Message-ID: <20070528091118.GA12886@gmail.com> (raw)
In-Reply-To: <20070527065202.GA6908@gmail.com>
On Sun, May 27, 2007 at 08:52:02AM +0200, Gregoire Favre wrote:
Oops,
i was wrong : I did patch my 2.6.21.1 with x86_64-mm-vmalloc-32.patch :
Fix vmalloc_32 to really allocate <4GB on 64bit platforms
Ugly ifdef, but should handle all 64bit platforms that have suitable
zones. On some like Altix it's probably impossible without IOMMU
use to get memory <4GB this way, but they have to live with that.
Signed-off-by: Andi Kleen <ak@suse.de>
And I don't remember exactly what else (in case that needed I could look
at my email archive) but the bug that was found in 2.6.21 regarding the
use of system with 4Gb is still present in 2.6.21.3 : is that something
that was forgotten to be included ?
Please CC to me all lkml answer as I am not on lkml, thank.
> Hello,
>
> I thought my budget Geniatech DVB-S was out of order, because there was
> high lightning, but it's not the case.
>
> Under 2.6.21.1 with included dvb driver and with hg drivers (a little
> bit outdated) my budget-av and my cx88 card works just great.
>
> Under 2.6.21.3 with included dvb driver and with hg drivers (up to date
> from yesterday) my budget-av works just great, but the cx88 can only
> tune but don't deliver anything ???
>
> In case that matter I am under 64 bits (Core 2 Duo).
>
> Anyone got an idea what might cause this ?
> --
> Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org
> http://picasaweb.google.com/Gregoire.Favre
--
Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org
http://picasaweb.google.com/Gregoire.Favre
parent reply other threads:[~2007-05-28 9:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20070527065202.GA6908@gmail.com>]
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=20070528091118.GA12886@gmail.com \
--to=gregoire.favre@gmail.com \
--cc=ak@suse.de \
--cc=linux-dvb@linuxtv.org \
--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