18 Mar, 2014
9 commits
-
At present we use U-Boot's filesystem layer to read the sandbox device tree,
but this is problematic since it relies on a temporary feauture added
there. Since we plan to implement proper block layer support for sandbox,
change this code to use the os layer functions instead. Also use the new
fdt_create_empty_tree() instead of our own code.Signed-off-by: Simon Glass
-
The current 4MB size is a little small for some tests, so increase it.
Reviewed-by: Hung-ying Tyan
Signed-off-by: Simon Glass -
This function does not actually change the pointer contents, so use const
so that functions which have a const pointer do not need to cast.Signed-off-by: Simon Glass
-
The commit 6af8dc3ebccb3b1e4b2e479315e49545e7f53150 broke support for
S25FL032P and S25FL064P by carelessly removing the code handling special
page size for these two SPI NOR flashes and unifying the code under the
assumption that Extended JEDEC ID of 0x4d00 always implies 512b page size.Add special case handling for these two SPI NOR flashes.
Signed-off-by: Marek Vasut
Reviewed-by: Jagannadha Sutradharudu Teki -
Refactor the code a bit to make it better in readability.
Remove the comments because now the intention of the code is pretty clear.Signed-off-by: Axel Lin
Reviewed-by: Jagannadha Sutradharudu Teki -
Squash the malloc()+memset() combo in favor of calloc().
Signed-off-by: Jagannadha Sutradharudu Teki
Acked-by: Marek Vasut -
Squash the malloc()+memset() combo in favor of calloc().
Signed-off-by: Marek Vasut
Reviewed-by: Jagannadha Sutradharudu Teki -
Add IDs for this new chip.
Signed-off-by: Marek Vasut
Reviewed-by: Jagannadha Sutradharudu Teki -
Both of these chips have 256kB big sectors, thus the _256K suffix,
compared to their _64K counterparts, which have 64kB sectors. Also,
they have four times less sectors than their _64K counterparts.Signed-off-by: Marek Vasut
Tested-by: Jagannadha Sutradharudu Teki
14 Mar, 2014
2 commits
-
romImage is set by CONFIG_ECOVEC_ROMIMAGE_ADDR to 0xA0040000.
Signed-off-by: Baruch Siach
Signed-off-by: Nobuhiro Iwamatsu -
Add missing port X data register, and fix the offset of ports Y and Z.
Signed-off-by: Baruch Siach
Signed-off-by: Nobuhiro Iwamatsu
13 Mar, 2014
21 commits
-
The tools "buildman" and "patman" are written in Python.
When we run them, "*.pyc" files are created under
tools/buildman, tools/patman directories.They should be cleaned up by "make distclean".
Signed-off-by: Masahiro Yamada
Cc: Tom Rini
Acked-by: Simon Glass -
These variable are no longer used.
Signed-off-by: Masahiro Yamada
-
Prior to Kbuild, $(OBJTREE) was used for pointing to the
top of build directory with absolute path.In Kbuild style, $(objtree) is used instead.
This commit renames OBJTREE to objtree and delete the
defition of OBJTREE.Signed-off-by: Masahiro Yamada
-
Prior to Kbuild, $(TOPDIR) or $(SRCTREE) was used for
pointing to the top of source directory.
(No difference between the two.)In Kbuild style, $(srctree) is used for instead.
This commit renames SRCTREE to srctree and deletes the
defition of SRCTREE.Note that SRCTREE in scripts/kernel-doc, scripts/docproc.c,
doc/DocBook/Makefile should be keep.Signed-off-by: Masahiro Yamada
-
Prior to Kbuild, $(TOPDIR) or $(SRCTREE) was used for
pointing to the top of source directory.
(No difference between the two.)In Kbuild style, $(srctree) is used instead.
This commit renames TOPDIR to srctree and delete the
defition of TOPDIR.Signed-off-by: Masahiro Yamada
-
Non-empty $(KBUILD_SRC) means out-of-tree build.
Signed-off-by: Masahiro Yamada
-
Pull out "$(SRCTREE)/" from CONFIG_SYS_KWD_CONFIG
and push it into the top Makefile.Signed-off-by: Masahiro Yamada
Cc: Michael Walle
Cc: Simon Guinot
Cc: Dave Purdy
Cc: Stefan Herbrechtsmeier
Cc: Luka Perkov
Cc: Valentin Longchamp
Cc: Jason Cooper
Cc: Siddarth Gore
Cc: Prafulla Wadaskar
Cc: Eric Cooper
Cc: Suriyan Ramasami -
Pull out "$(SRCTREE)/" from CONFIG_SYS_FSL_PBL_PBI
and CONFIG_SYS_FSL_PBL_RCW and push it into the top Makefile.Signed-off-by: Masahiro Yamada
Cc: York Sun
Cc: Poonam Aggrwal
Cc: Valentin Longchamp -
$(SRCTREE)/$(CPUDIR)/u-boot.lds is our default location
of arch-specific linker script.Remove redundant definitions in
arch/{arc,microblaze,openrisc}/config.mk.Signed-off-by: Masahiro Yamada
Cc: Alexey Brodkin
Cc: Stefan Kristiansson
Acked-by: Michal Simek -
Signed-off-by: Masahiro Yamada
Cc: Simon Glass -
Signed-off-by: Masahiro Yamada
Cc: Simon Glass -
Signed-off-by: Masahiro Yamada
Cc: David Updegraff
Cc: Andre Schwarz -
Signed-off-by: Masahiro Yamada
Cc: Fabio Estevam
Cc: Otavio Salvador
Cc: Lauri Hintsala
Acked-by: Marek Vasut -
- extend the discussion of USB network related config options such that
all available adapter drivers are listed, and that the 'usb' command
for the interactive prompt and scripting becomes available
- suggest to *not* put individual IP configuration parameters into the
exectuable, but instead to put them into external environment or fetch
them from networkSigned-off-by: Gerhard Sittig
Acked-by: Simon Glass
Acked-by: Marek Vasut -
enabling CONFIG_MACB makes other locations in the stamp config file
enable network related commands (actually prevents disabling them)enable USB ethernet support by activating generic support as well as
Asix and Moschip ethernet adaptersSigned-off-by: Gerhard Sittig
Acked-by: Andreas Bießman -
enable support for the Moschip USB ethernet adapter for those boards
which previously had support for "all other" USB ethernet adapters
(that's Asix _and_ SMSC) enabled -- which applies to harmony, m53evk,
mx53loco, nitrogen6x, omap3_beagleSigned-off-by: Gerhard Sittig
Acked-by: Marek Vasut -
adjust the harmony and omap3_beagle board configs to make
their CONFIG_USB_ETHER_* items appear in alphabetical orderSigned-off-by: Gerhard Sittig
Acked-by: Simon Glass
Acked-by: Marek Vasut -
introduce an 'mcs7830' driver for Moschip MCS7830 based (7730/7830/7832)
USB 2.0 Ethernet Devicessee "MCS7830 -- USB 2.0 to 10/100M Fast Ethernet Controller" at
http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=109;74;109the driver was implemented based on the U-Boot Asix driver with
additional information gathered from the Moschip Linux driver,
development was done on "Delock 61147" and "Logilink UA0025C" donglesSigned-off-by: Gerhard Sittig
Acked-by: Marek Vasut -
while compilation of implemented routines and references from calling
sites may be optional, declarations in header files should not beunconditionally declare the Asix and SMSC related public USB ethernet
driver routines in the usb_ether.h header fileSigned-off-by: Gerhard Sittig
Acked-by: Simon Glass
Acked-by: Marek Vasut -
Some NOR flash devices have a small erase block size. For example, the
Micron N25Q512 can erase in 4K blocks. These devices expose a bug in
fw_env.c where flash_write_buf() incorrectly calculates bytes written
and attempts to write past the environment sectors. Luckily, a range
check prevents any real damage, but this does cause fw_setenv to fail
with an error.This change corrects the write length calculation.
The bug was introduced with commit 56086921 from 2008 and only affects
configurations where the erase block size is smaller than the total
environment data size.Signed-off-by: Dustin Byford
-
The assumed number of environment sectors (always 1) leads to an
incorrect top_of_range calculation in fw.env.c when a flash device has
an erase block size smaller than the environment data size (number of
environment sectors > 1).This change updates the default number of environment sectors to at
least cover the size of the environment.Also corrected a false statement about the number of sectors column in
fw_env.config.Signed-off-by: Dustin Byford
11 Mar, 2014
8 commits
-
Some recent changes got parts of the file out of order again, correct.
Signed-off-by: Tom Rini
-
When I cc board maintainers, some of them result in
bounce mails.It turned out the following do not work any more:
Yuli Barcohen
Travis Sawyer
Yusdi Santoso
David Updegraff
Sangmoon Kim
Anton Vorontsov
Blackfin Team
Bluetechnix Tinyboards
Andre SchwarzFor the blackfin boards where Sonic Zhang is also listed
as a maintainer, dead addresses should be simply dropped.For all of the others, the status should be changed to "Orphan".
We have adopted the definition of "Orphan" as:
board is not actively maintained any more but still builds, and any
address associated with it is that of the last known maintainer(s)Even though the emails do not work any more, they carry information.
We want to keep them.Besides, Orphan boards have been collected at the bottom of boards.cfg.
(This is done when we run "tools/reformat.py")Add separators to distinguish them from those which
were moved to Orphan 6 months ago.
I believe it will be helpful in future to find which boards are
old enough to be removed from the code base.Signed-off-by: Masahiro Yamada
Cc: Detlev Zundel
Cc: Tom Rini
Cc: Albert ARIBAUD -
Signed-off-by: Tom Rini
-
Many USB host controller drivers contain almost identical copies of the
same virtual root hub descriptors. Put these into a common file to avoid
duplication.Note that there were some very minor differences between the descriptors
in the various files, such as:- USB 1.0 vs. USB 1.1
- Manufacturer/Device ID
- Max packet size
- String contentI assume these aren't relevant.
Cc: Thomas Lange
Cc: Shinya Kuribayashi
Cc: Gary Jennejohn
Cc: Wolfgang Denk
Cc: Eric Millbrandt
Cc: Pierre Aubert
Cc: Stefan Roese
Cc: Daniel Hellstrom
Cc: Denis Peter
Cc: Rodolfo Giometti
Cc: Zhang Wei
Cc: Mateusz Zalega
Cc: Remy Bohmer
Cc: Markus Klotzbuecher
Cc: Minkyu Kang
Cc: Gary Jennejohn
Cc: C Nauman
Cc: David Müller
Cc: Yoshihiro Shimoda
Cc: Nobuhiro Iwamatsu
Cc: Thomas Abraham
Cc: Tom Rini
Cc: Andrew Murray
Cc: Matej Frančeškin
Cc: Cliff Cai
Cc: Bryan Wu
Signed-off-by: Stephen Warren -
These data structures are passed to cache-flushing routines, and hence
must be conform to both the USB the cache-flusing alignment requirements.
That means aligning to USB_DMA_MINALIGN. This is important on systems
where cache lines are >32 bytes.Signed-off-by: Stephen Warren
-
Section 4.10.2 "Advance Queue" of ehci-specification-for-usb.pdf
specifies how an EHCI controller loads a new QTD for processing if the
QH is not already marked as active. It states:=====
If the field Bytes to Transfer is not zero and the T-bit in the Alternate
Next qTD Pointer is set to zero, then the host controller uses the
Alternate Next qTD Pointer. Otherwise, the host controller uses the Next
qTD Pointer. If Next qTD Pointer’s T-bit is set to a one, then the host
controller exits this state and uses the horizontal pointer to the next
schedule data structure.
=====Hence, we must ensure that the alternate next QTD pointer's T-bit
(TERMINATE) is set, so the EHCI controller knows to use the next QTD
pointer.Signed-off-by: Stephen Warren
