All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, ak@linux.intel.com,
	dwmw2@infradead.org, hancockrwd@gmail.com,
	Larry.Finger@lwfinger.net
Subject: Re: b44 driver causes panic when using swiotlb
Date: Tue, 15 Feb 2011 17:03:11 -0500	[thread overview]
Message-ID: <20110215170311.512b86f7@katamari> (raw)
In-Reply-To: <20110214205945W.fujita.tomonori@lab.ntt.co.jp>

On Mon, 14 Feb 2011 20:59:43 +0900
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:

> > Can you try this? b44 has the own bouncing mechanism so if swiotlb
> > returns an error, the driver can allocate an appropriate buffer.
> > 
> > diff --git a/lib/swiotlb.c b/lib/swiotlb.c
> > index c47bbe1..93ca08b 100644
> > --- a/lib/swiotlb.c
> > +++ b/lib/swiotlb.c
> > @@ -686,8 +686,10 @@ dma_addr_t swiotlb_map_page(struct device *dev, struct page *page,
> >  	/*
> >  	 * Ensure that the address returned is DMA'ble
> >  	 */
> > -	if (!dma_capable(dev, dev_addr, size))
> > -		panic("map_single: bounce buffer is not DMA'ble");
> > +	if (!dma_capable(dev, dev_addr, size)) {
> > +		swiotlb_tbl_unmap_single(dev, map, size, dir);
> > +		dev_addr = swiotlb_virt_to_bus(dev, io_tlb_overflow_buffer);
> > +	}
> >  
> >  	return dev_addr;
> >  }
> 
> Ping, any chance to try this?

The user who reported the bug tried it and says that it works.

  parent reply	other threads:[~2011-02-15 22:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 15:54 b44 driver causes panic when using swiotlb Chuck Ebbert
2011-01-31 16:36 ` Andi Kleen
2011-02-01  0:54   ` Robert Hancock
2011-02-01  1:28     ` FUJITA Tomonori
2011-02-01  3:22       ` Robert Hancock
2011-02-01  5:22         ` FUJITA Tomonori
2011-02-15  0:47           ` Robert Hancock
2011-02-01 21:18       ` Chuck Ebbert
2011-02-02  0:06         ` FUJITA Tomonori
2011-02-02  0:09           ` FUJITA Tomonori
2011-02-01 18:07     ` Andi Kleen
2011-02-01 21:44       ` Robert Hancock
2011-02-01 13:54 ` FUJITA Tomonori
2011-02-14 11:59   ` FUJITA Tomonori
2011-02-14 16:41     ` Arkadiusz Miśkiewicz
2011-02-15  0:39       ` FUJITA Tomonori
2011-02-15 22:03     ` Chuck Ebbert [this message]
     [not found] <4D478EDC.4070004@lwfinger.net>
2011-02-01  4:53 ` Larry Finger

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=20110215170311.512b86f7@katamari \
    --to=cebbert@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=ak@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hancockrwd@gmail.com \
    --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 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.