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] [thread-next>] [day] [month] [year] [list]
Message-Id: <200903210747.AA00743@cj3020122-b.jcom.home.ne.jp>
Date:	Sat, 21 Mar 2009 16:47:47 +0900
From:	yamazaki <yamazaki-seiji@...m.home.ne.jp>
To:	avorontsov@...mvista.com
Cc:	sdhci-devel@...t.drzeus.cx, Arnd Bergmann <arnd@...db.de>,
	Liu Dave <DaveLiu@...escale.com>, linux-kernel@...r.kernel.org,
	linuxppc-dev@...abs.org, Ben Dooks <ben-linux@...ff.org>,
	Pierre Ossman <drzeus-sdhci@...eus.cx>
Subject: Re: [PATCH 11/11] mmc: Add OpenFirmware bindings for SDHCI driver

Hi 

Thank you for your reply again.

>Ah, then it must be connected via MPC8347's localbus.

That's right.

I will try it,and I inform them of the result. 

>On Sat, Mar 21, 2009 at 09:15:25AM +0900, yamazaki wrote:
>> Hi 
>> 
>> Thank you for your reply.
>> I know RICOH has PCI SD/MMC controller. But R5C807 RICOH is not the PCI device
>> which is probably new product.
>
>Ah, then it must be connected via MPC8347's localbus.
>
>Well, then you need 2.6.29-rcX kernels, for example
>http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.29-rc8.tar.bz2
>is suitable.
>
>Untar it and apply the patches (they'll apply fine on that
>kernel). Then you'll need some device tree additions for
>your MPC8347 board, something like this:
>
>        localbus@...05000 {
>                #address-cells = <2>;
>                #size-cells = <1>;
>                compatible = "fsl,mpc8347-localbus",
>                             "fsl,pq2pro-localbus";
>                reg = <0xe0005000 0xd8>;
>                ranges = <0x1 0x0 0xf0000000 0x1000>;
>		// ^^ change the 0xf0000000 to the actual address
>                sdhci@1,0 {
>                        compatible = "ricoh,r5c807", "generic-sdhci";
>                        reg = <0x1 0x0 0x1000>;
>                        interrupts = <ricoh-interrupt-here 0x8>;
>                        interrupt-parent = <&ipic>;
>                        // if needed, clock-frequency = <freq-in-HZ-here>;
>                };
>        };
>
>Note that I'm not sure what endiannes you'll get when connecting
>the ricoh chip to the big-endinan host...
>
>-- 
>Anton Vorontsov
>email: cbouatmailru@...il.com
>irc://irc.freenode.net/bd2

----
yamazaki-seiji@...m.home.ne.jp
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ