From: Jon Burgess <jburgess777@googlemail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Markus Rechberger <mrechberger@gmail.com>,
Gregoire Favre <Gregoire.Favre@gmail.com>,
linux-dvb@linuxtv.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-dvb] Re: More than 2Gb problem (dvb related) ?
Date: Fri, 27 Apr 2007 23:37:26 +0100 [thread overview]
Message-ID: <1177713446.7205.3.camel@localhost.localdomain> (raw)
In-Reply-To: <75b66ecd0704271506x595dfb6bqe0ef4fd153818501@mail.gmail.com>
On Fri, 2007-04-27 at 18:06 -0400, Lee Revell wrote:
> On 4/27/07, Jon Burgess <jburgess777@googlemail.com> wrote:
> > Interesting - I see similar symptoms after upgrading my PC:
> > * old PC was AMD Athlon 64 3000 w/ 2GB of RAM which had no issues
> > * new PC is a Intel Core 2 Duo w/ 4GB of RAM and fails in the way you
> > describe.
>
> Driver using an incorrect DMA mask?
>
> Lee
It does not set one explicitly and the docs suggest the default is
32bit. Adding an explicit "pci_set_dma_mask(dev->pci, DMA_24BIT_MASK)"
does not seem to make a difference. Mind you, the driver builds its own
S-G DMA table in saa7146_vmalloc_build_pgtable() and i'm not certain
whether this might bypass this setting.
Jon
next prev parent reply other threads:[~2007-04-27 22:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 11:10 More than 2Gb problem (dvb related) ? Gregoire Favre
2007-04-27 20:46 ` Markus Rechberger
2007-04-27 21:03 ` Gregoire Favre
2007-04-27 22:00 ` [linux-dvb] " Jon Burgess
2007-04-27 22:06 ` Lee Revell
2007-04-27 22:37 ` Jon Burgess [this message]
2007-04-28 17:17 ` [PATCH] " Jon Burgess
2007-04-28 20:14 ` Jon Burgess
2007-04-29 14:07 ` Gregoire Favre
2007-04-30 0:22 ` [linux-dvb] " Oliver Endriss
2007-04-30 16:52 ` Gregoire Favre
2007-04-30 18:05 ` Jon Burgess
2007-05-01 9:39 ` Gregoire Favre
2007-05-01 9:41 ` Gregoire Favre
2007-05-01 22:11 ` Jon Burgess
2007-05-02 9:35 ` Andi Kleen
2007-05-02 12:17 ` Gregoire Favre
2007-05-05 7:36 ` Gregoire Favre
2007-05-01 15:58 ` [linux-dvb] " Oliver Endriss
2007-05-01 20:03 ` Gregoire Favre
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=1177713446.7205.3.camel@localhost.localdomain \
--to=jburgess777@googlemail.com \
--cc=Gregoire.Favre@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrechberger@gmail.com \
--cc=rlrevell@joe-job.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 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.