From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bin Meng Date: Mon, 4 Jan 2016 16:31:05 +0800 Subject: [U-Boot] Pull request: u-boot-net In-Reply-To: References: <20160102170929.GW4093@bill-the-cat> <20160104034659.GA4093@bill-the-cat> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Jan 4, 2016 at 11:56 AM, Bin Meng wrote: > +Simon, > > Hi Tom, > > On Mon, Jan 4, 2016 at 11:46 AM, Tom Rini wrote: >> On Mon, Jan 04, 2016 at 10:35:39AM +0800, Bin Meng wrote: >>> +Dirk >>> >>> On Sun, Jan 3, 2016 at 1:09 AM, Tom Rini wrote: >>> > On Tue, Dec 22, 2015 at 11:58:01AM -0600, Joe Hershberger wrote: >>> > >>> >> A few patches that came in during the merge window and appear harmless. >>> >> >>> >> These cause no additional build warnings or errors. >>> >> >>> >> Thanks, >>> >> -Joe >>> >> >>> >> The following changes since commit 4832e17787acb29734d895751bc7a594908aecc6: >>> >> >>> >> Merge branch 'master' of git://www.denx.de/git/u-boot-microblaze >>> >> (2015-12-18 07:28:24 -0500) >>> >> >>> >> are available in the git repository at: >>> >> >>> >> >>> >> git://git.denx.de/u-boot-net.git master >>> >> >>> >> for you to fetch changes up to 140bc33e05382545b762ef51d6fc31dd5b6ec82c: >>> >> >>> >> net: e1000: Mark _disable_wr() and _write_status() as __maybe_unused >>> >> (2015-12-21 20:01:57 -0600) >>> >> >>> >> ---------------------------------------------------------------- >>> >> Bin Meng (5): >>> >> fdt: Deprecate "usbethaddr" usage in fdt_fixup_ethernet() >>> >> fdt: Rewrite the logic in fdt_fixup_ethernet() >>> >> net: e1000: Remove dead codes wrapped by #if 0 >>> >> net: e1000: Remove CONFIG_MVBC_1G >>> >> net: e1000: Mark _disable_wr() and _write_status() as __maybe_unused >>> >> >>> >> Fabio Estevam (1): >>> >> include: net: Simplify the usage of __always_inline >>> >> >>> >> common/fdt_support.c | 64 ++++++++++++++++++++-------------------- >>> >> drivers/net/e1000.c | 77 +------------------------------------------------ >>> >> drivers/net/e1000.h | 31 -------------------- >>> >> drivers/net/e1000_spi.c | 9 +++--- >>> >> include/net.h | 9 +++--- >>> >> 5 files changed, 42 insertions(+), 148 deletions(-) >>> > >>> > I think at this stage in the release we need to rework this and drop the >>> > fdt patches, or defer the whole thing until we can figure out some way >>> > to fit iocon in with the ELDK 5.6 toolchains. Thanks! >>> >>> I cannot reproduce this with the kernel.org powerpc gcc 4.9 toolchain. >>> I am downloading ELDK 5.6 toolchain to see what's going on there. >>> IMHO, we should increase the iocon's U-Boot size to 512K. I see from >>> its iocon.h file its flash size is 64MB, which has plenty of spaces to >>> store a bigger U-Boot. Even if we try our best to rework this fdt >>> patch, there is still possibility to break iocon sometime in the >>> future by some other random fixes or new features. This to me is a >>> tedious process. >> >> I don't know why this is so hard to reproduce, I also see it with the >> debian/unstable gcc 5.x toolchain I do beleive. >> > > Still downloading ELDK toolchains so cannot comment ELDK compiler > behavior :) One question, what's our recommended toolchains for > U-Boot? I have been using kernel.org toolchains as mentioned in the > buildman doc and some other ones mentioned in the moveconfig doc. > > The simple fix is to change change iocon to a more larger size since > it has a 64MB flash. Dirk, can you please comment? > I am having a hard time installing ELDK 5.6 with eldk-5.6-powerpc-4xx.iso on a CentOS machine. Firstly, I read the help by: $ ./install.sh -h Usage: install.sh [-D] [-d ] [-a ] [-s ] [-r ] [] install.sh -l [] install.sh -h -D: Dry-run: display commands, but don't actually execute them. -a: SDK host architecture. Chose one of 'i686' or 'x86_64". Defaults to "i686". -d: Destination directory. Defaults to "/opt/eldk-5.6" -h: Help: print this message. -l: List available SDK and RFS images -s: Select SDK image. Chose one of 'toolchain', 'toolchain-qte', 'toolchain-qte-xenomai', or '-' for none. Defaults to "toolchain". -r: Select list of target RFS images. Chose one or more of 'minimal', 'minimal-mtdutils', 'minimal-dev', 'minimal-xenomai', 'base', 'basic', 'clutter', 'lsb', 'lsb-dev', 'lsb-sdk', 'sato', 'sato-dev', 'sato-sdk', 'qte-sdk', 'qte-xenomai-sdk', 'x11', or '-' for none. Defaults to all. target architecture, defaults to "armv7a-hf" Then I did: $ ./install.sh -d /share/toolchain/eldk-5.6 -r - -a x86_64 powerpc-4xx Error: SDK image "gmae" is not available Available SDK images for target 'powerpc-4xx': Then I did: $ ./install.sh -d /share/toolchain/eldk-5.6 -s toolchain -r - -a x86_64 powerpc-4xx Error: SDK image "toolchain" is not available Available SDK images for target 'powerpc-4xx': Nothing helpful was shown on the console until I figured it out I should pass '-a i686' :( $ ./install.sh -d /share/toolchain/eldk-5.6 -s toolchain -r - -a i686 powerpc-4xx *** Installing ./targets/powerpc-4xx/eldk-eglibc-i686-powerpc-toolchain-5.6.sh into /share/toolchain/eldk-5.6/powerpc-4xx tar: ./sysroots: Cannot mkdir: Read-only file system tar: ./sysroots/ppc440e-linux: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/boot: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/bin: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/bin/.debug: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/lib: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/lib/.debug: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/lib/security: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/lib/security/.debug: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/lib/security/pam_filter: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/lib/security/pam_filter/.debug: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/etc: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/etc/pam.d: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/etc/security: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/etc/security/namespace.d: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/etc/security/limits.d: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/etc/default: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/etc/default/volatiles: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/etc/terminfo: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/etc/terminfo/v: Cannot mkdir: No such file or directory tar: ./sysroots/ppc440e-linux/etc/terminfo/s: Cannot mkdir: No such file or directory <......> Lots of 'Cannot mkdir: No such file or directory' message are shown on the console. I am pretty sure I have RW rights on the /share/toolchain/eldk-5.6 directory. Anything I am missing here? Regards, Bin