LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "rubisher" <rubisher@scarlet.be>
To: "fujita\.tomonori" <fujita.tomonori@lab.ntt.co.jp>
Cc: "tomof" <tomof@acm.org>, "kyle" <kyle@mcmartin.ca>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"linux-parisc" <linux-parisc@vger.kernel.org>,
"tomof" <tomof@acm.org>, "kyle" <kyle@parisc-linux.org>,
"matthew" <matthew@wil.cx>,
"grundler" <grundler@parisc-linux.org>,
"akpm" <akpm@linux-foundation.org>,
"fujita\.tomonori" <fujita.tomonori@lab.ntt.co.jp>,
"rubisher" <rubisher@scarlet.be>
Subject: Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
Date: Tue, 4 Mar 2008 17:13:55 +0100 [thread overview]
Message-ID: <JX7RR7$3528E2939A349F65E12E3F27315EEC50@scarlet.be> (raw)
[snip]
> > Can you try the following patch? It's on the top of the patchset.
> >
> Good catch: now this first testing system (I mean the b2k) is up and running ;-)
>
> I will now try the ccio_dma driver on a d380 ...
>
Yes, it works too on a d380 boxe running a 32bit up kernel.
Btw (it was a long time ago), I also resurrect my 64 config for the b2k model
and it also works fine.
Many tx again,
r.
> hth,
> r.
>
> > Thanks,
> >
> > diff --git a/drivers/parisc/ccio-dma.c b/drivers/parisc/ccio-dma.c
> > index 2f3b364..d0855a1 100644
> > --- a/drivers/parisc/ccio-dma.c
> > +++ b/drivers/parisc/ccio-dma.c
> > @@ -366,8 +366,8 @@ ccio_alloc_range(struct ioc *ioc, struct device *dev,
> size_t size)
> > ** ggg sacrifices another 710 to the computer gods.
> > */
> >
> > - boundary_size = ALIGN(dma_get_seg_boundary(dev) + 1, 1 << IOVP_SHIFT);
> > - boundary_size >>= IOVP_SHIFT;
> > + boundary_size = ALIGN((unsigned long long)dma_get_seg_boundary(dev) + 1,
> > + 1ULL << IOVP_SHIFT) >> IOVP_SHIFT;
> >
> > if (pages_needed <= 8) {
> > /*
> > diff --git a/drivers/parisc/sba_iommu.c b/drivers/parisc/sba_iommu.c
> > index e834127..bdbe780 100644
> > --- a/drivers/parisc/sba_iommu.c
> > +++ b/drivers/parisc/sba_iommu.c
> > @@ -341,8 +341,8 @@ sba_search_bitmap(struct ioc *ioc, struct device *dev,
> > unsigned long shift;
> > int ret;
> >
> > - boundary_size = ALIGN(dma_get_seg_boundary(dev) + 1, 1 << IOVP_SHIFT);
> > - boundary_size >>= IOVP_SHIFT;
> > + boundary_size = ALIGN((unsigned long long)dma_get_seg_boundary(dev) + 1,
> > + 1ULL << IOVP_SHIFT) >> IOVP_SHIFT;
> >
> > #if defined(ZX1_SUPPORT)
> > BUG_ON(ioc->ibase & ~IOVP_MASK);
> > --
---
Scarlet One, ADSL 6 Mbps + Telephone, from EUR 29,95...
http://www.scarlet.be/
next reply other threads:[~2008-03-04 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 16:13 rubisher [this message]
2008-03-05 2:56 ` FUJITA Tomonori
-- strict thread matches above, loose matches on Subject: below --
2008-03-03 14:43 rubisher
2008-03-03 11:04 rubisher
2008-03-03 12:22 ` FUJITA Tomonori
2008-03-03 10:36 rubisher
2008-03-02 6:10 FUJITA Tomonori
2008-03-02 17:13 ` Kyle McMartin
2008-03-05 3:54 ` FUJITA Tomonori
2008-03-05 15:45 ` Grant Grundler
2008-03-06 0:19 ` John David Anglin
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='JX7RR7$3528E2939A349F65E12E3F27315EEC50@scarlet.be' \
--to=rubisher@scarlet.be \
--cc=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=grundler@parisc-linux.org \
--cc=kyle@mcmartin.ca \
--cc=kyle@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=tomof@acm.org \
--subject='Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).