linux-kernel - Re: [PATCH 0/3] MIPS: Extend plat

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090424042310.GA19096@linux-mips.org>
Date:	Fri, 24 Apr 2009 06:23:10 +0200
From:	Ralf Baechle <ralf@...ux-mips.org>
To:	Kevin Cernekee <cernekee@...il.com>
Cc:	linux-mips@...ux-mips.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] MIPS: Extend plat_* abstractions, cache support

On Thu, Apr 23, 2009 at 05:03:43PM -0700, Kevin Cernekee wrote:

> I am upgrading an SoC to the 2.6.29.1 kernel from an earlier version,
> and in the process I am switching over the old board support
> customizations to use the newer, cleaner plat_* functions.  I found two
> cases where the plat_* functions did not provide enough information,
> so I had to modify the API:
> 
> plat_unmap_dma_mem() - Our handler needs to know the size and direction
> of the DMA mapping.  This information is not encoded in the DMA address,
> so it needed to be passed in explicitly.
> 
> plat_dma_addr_to_phys() - The bus<->physical address mappings differ
> based on which bus is being used.  It is not always possible to infer
> which bus is being used from the bus address alone, so I added a
> "struct device" to the function definition.
> 
> Also, our MIPS core uses 64-byte D$ lines, so I needed to generate the
> corresponding blast* functions.
> 
> These patches apply against the linux-mips.org GIT tree.

Queued for 2.6.31.  Thanks Kevin!

Which SoC port are you working on btw?

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/