All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@petalogix.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] arch/microblaze fixes for 2.6.35-rc3 v2
Date: Tue, 08 Jun 2010 12:28:53 +0200	[thread overview]
Message-ID: <4C0E1B65.9000603@petalogix.com> (raw)
In-Reply-To: <20100608083015L.fujita.tomonori@lab.ntt.co.jp>

FUJITA Tomonori wrote:
> On Mon, 07 Jun 2010 20:20:03 +0200
> Michal Simek <michal.simek@petalogix.com> wrote:
> 
>> Hi Linus,
>>
>> here are only fixes for Microblaze. There is no any new features. 
>> (flush_dcache_page patch fix problem on WB system)
>> Just note: Some new patches broke Microblaze arch that's why I would 
>> like to add at least these patches to your tree.
>>
>> Thanks,
>> Michal
>>
>>
>> The following changes since commit 386f40c86d6c8d5b717ef20620af1a750d0dacb4:
>>    Linus Torvalds (1):
>>          Revert "tty: fix a little bug in scrup, vt.c"
>>
>> are available in the git repository at:
>>
>>    git://git.monstr.eu/linux-2.6-microblaze.git next
>>
>> Michal Simek (7):
>>        microblaze: Fix __copy_to/from_user_inatomic macros
>>        microblaze: Sync noMMU and MMU setup_memory
>>        microblaze: Fix comment for TLB
>>        microblaze: Implement flush_dcache_page macro
>>        microblaze: Enable NEED_SG_DMA_LENGTH
> 
> Sorry, my scatterlist patchset breaks microblaze?

yes, it does.
http://www.monstr.eu/wiki/doku.php?id=log:2010-06-07_12_23_12#folded_17

> 
> Seems that microblaze can simply remove sg->dma_length instead of
> enabling NEED_SG_DMA_LENGTH. If sg->dma_length is always equal to
> sg->length on your architecture, you don't need to waste memory for
> sg->dma_length.

Please correct me if I am wrong. dma_length is used for 64bit machines.
Microblaze is "only" 32bit.

Can you please generate proper patch?

Thanks,
Michal


> 
> 
> diff --git a/arch/microblaze/kernel/dma.c b/arch/microblaze/kernel/dma.c
> index 9dcd90b..79c7465 100644
> --- a/arch/microblaze/kernel/dma.c
> +++ b/arch/microblaze/kernel/dma.c
> @@ -90,7 +90,6 @@ static int dma_direct_map_sg(struct device *dev, struct scatterlist *sgl,
>  	/* FIXME this part of code is untested */
>  	for_each_sg(sgl, sg, nents, i) {
>  		sg->dma_address = sg_phys(sg) + get_dma_direct_offset(dev);
> -		sg->dma_length = sg->length;
>  		__dma_sync_page(page_to_phys(sg_page(sg)), sg->offset,
>  							sg->length, direction);
>  	}


-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663

  reply	other threads:[~2010-06-08 10:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 18:20 [GIT PULL] arch/microblaze fixes for 2.6.35-rc3 v2 Michal Simek
2010-06-07 23:31 ` FUJITA Tomonori
2010-06-08 10:28   ` Michal Simek [this message]
2010-06-08 11:03     ` FUJITA Tomonori
2010-06-08 20:14 ` Linus Torvalds
2010-06-08 20:36   ` Geert Uytterhoeven
2010-06-09  0:29     ` Linus Torvalds
2010-06-09 11:04       ` Michal Simek

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=4C0E1B65.9000603@petalogix.com \
    --to=michal.simek@petalogix.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --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.