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>] [day] [month] [year] [list]
Message-ID: <54D490BE.9040201@gmail.com>
Date:	Fri, 06 Feb 2015 11:00:30 +0100
From:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To:	Gabriel Dobato <dobatog@...il.com>,
	Jean-Francois Moine <moinejf@...e.fr>
CC:	Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Jason Cooper <jason@...edaemon.net>,
	Andrew Lunn <andrew@...n.ch>,
	Gregory Clement <gregory.clement@...e-electrons.com>
Subject: Re: [PATCH] ARM: dts: mvebu: add ethernet to the cm-a510 board

On 06.02.2015 10:19, Gabriel Dobato wrote:
> On 05/02/15 23:13, Sebastian Hesselbarth wrote:
>> great you can boot a recent kernel. I guess you had to quite heavily
>> modify current dove-cm-a510.dts? Can you upload the one you use now
>> to any pastebin and send the link?
>
> Not, I only had to include eth (as Mr. Moine told me) and mdio because I
> mount rootfs via NFS.

Ok, I think we can work out the most obvious stuff (mmc, pcie), too.

>> You didn't mention if you really use the sb-a510, i.e. the Compulab
>> reference baseboard. Is it what you are using with your cm-a510?
>
> Yes, sorry for that, I am using SB-A510.

Ok. Then for the first some versions, I'll stick with the manual.
That should be sufficient to create a working sb-a510 dts.

FWIW, is there any Compulab kernel or u-boot source available online?
It would help to figure out the GPIO pins and undocumented connections.

> I wonder if it will there be driver support for the second ethernet
> (PCIE attached NIC), and the rest of features remained, for DT...

AFAIR it was some realtek PCIe NIC.. we have PCIe working on Dove, so
I guess it shouldn't be a real problem.

> Before using DT, I tried to boot a simple uImage (without DT), but it
> did not boot
>
> the last ouput in the kernel trade was:
> ...
> /uncompressing linux... done, booting the kernel./
>
> nothing else.... I wonder if there is a problem with the ID machine, I
> don't know...

Hard to tell. Could be anything.

> The U-Boot used was the one provided by Compulab (Maybe the problem is
> on Uboot...)

If you know how to append the dtb to the zImage it should work on any
u-boot. If it doesn't support bootz, you'll have to make a uImage of
the dtb-appended zImage or simply try to "go" to the zImage address.

Sebastian
--
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