| Age | Commit message (Collapse) | Author |
|---|
|
Add an explicit cast to avoid the following build warning:
colibri_vf.c:225:23: warning: initialization makes pointer from integer
without a cast [enabled by default]
|
|
Now as the colibri_vf61 configuration supports memory size as well as
module type auto detection actually rename it to colibri_vf to be
universally used for Colibri VF50 as well as VF61.
|
|
Implement module type (e.g. VF50 vs. VF61) auto detection based on L2
cache availability. Set specific ARM core clock (e.g. 400 vs. 500 MHz)
as well as Linux machine id number.
While at it actually use memargs instead of hard-coded mem= value.
While at it fix sdboot command if initially booting U-Boot from NAND by
doing an explicit mmc part 0.
|
|
Implement memory size auto detection including memargs generation
analogous to how it was done for Apalis/Colibri T20/T30.
While at it make our board file checkpatch compliant.
|
|
Add initial Colibri VF61 support based off Timesys' implementation for
Freescale's Vybrid Tower System TWR-VF65GS10:
- New machine ID.
- Default UART_A on SCI0.
- ESDHC2 only.
- 8-bit NAND.
- No quad SPI.
- FEC1 only.
- Enabled command line editing.
- PLL5 based RMII clocking (e.g. no external crystal).
- UART_A, UART_B and UART_C I/O muxing.
- Increase the available space for the U-Boot binary to half a megabyte
by booting from gfxRAM rather than sysRAM0.
- Integrate factory configuration block handling for hardware version,
MAC address and serial number to be passed to Linux.
- The U-Boot environment is stored in NAND flash.
- Fix long standing boot hang issue introduced by Freescale's Vybrid
1.1 silicon.
- Proper 256 MB Nanya DDR3 RAM timings.
Tested on early Colibri VF61 prototypes V1.0b and V1.0c using SD card
(mandatory for initial loading) as well as NAND boot.
|
|
Fix long standing boot hang issue introduced by Freescale's Vybrid 1.1
silicon.
https://community.freescale.com/message/336513#336513
Correct Answer
by Ioseph Martinez Pelayo on Jul 17, 2013 5:33 PM
For the record:
DDRMC_CR154 needs to be 0x682C0000
before was: 0x68200000
There was a change from Si 1.0 to 1.1. So this only affects Si 1.1 and
this version requires writing this value to the register.
|
|
This reverts commit 9629454003a2f85dcff4410e4b56d27e1bde0dd0.
|
|
Fix the following build-time warning:
u-boot-toradex.git/include/configs/colibri_vf50_sdboot.h:54:0:
warning: "CONFIG_ENV_OFFSET" redefined [enabled by default]
|
|
Fix possible uninitialised array member issue in serial number to
hexadecimal coded decimal conversion routine.
|
|
Migrate to default NAND boot configuration (e.g. colibri_vf50_config)
and SD card boot on request (e.g. colibri_vf50_sdboot_config).
Automatically do the padding required for NAND boot image
(e.g. u-boot.nand).
This is also more in-line with how we did stuff back on the Colibri
T20.
|
|
Hack to avoid boot hang issue by just resetting for now if wrong memory
size is detected.
|
|
Integrate factory configuration block handling for hardware version,
MAC address and serial number to be passed to Linux.
The U-Boot environment is stored in NAND flash.
Default is to boot out of NAND flash using the UBI abstraction.
Optional NFS as well as MMC/SD boot variants are also available.
This brings the configuration more in-line with our Tegra based
versions.
While at it enable board size limit check set to 512 KB related to the
gfxRAM area of the OCRAM.
Please note that a boot delay of zero did not quite work the same way
as on the Tegras where one was still able to interrupt the boot process
by continuously hitting a key. Therefore set it to one second for now.
|
|
Increase the available space for the U-Boot binary to half a megabyte
by booting from gfxRAM rather than sysRAM0.
Please note that according to the Vybrid Reference Manual the bigger
lower part of the sysRAM1 which immediately follows sysRAM0 should be
available as well but testing showed that as soon as the U-Boot binary
got bigger than 256 KB booting failed.
|
|
Fix the following compile time warning:
colibri_vf50.c:392:32: warning: ‘index’ is used uninitialized in this
function [-Wuninitialized]
|
|
Add initial Colibri VF50 support based off Timesys' implementation for
Freescale's Vybrid Tower System TWR-VF65GS10:
- New machine ID.
- Default UART_A on SCI0.
- ESDHC2 only.
- 8-bit NAND.
- No quad SPI.
- FEC1 only.
- Enabled command line editing.
- PLL5 based RMII clocking (e.g. no external crystal).
- UART_A, UART_B and UART_C I/O muxing.
Tested on early Colibri VF50 prototypes V1.0a using SD card (mandatory
for initial loading) as well as NAND boot.
|
|
Add support for FEC1 only operation in case FEC0 is not used at all.
|
|
Add configuration option CONFIG_NAND_FSL_NFC_8BIT to be able to specify
narrow 8-bit wide bus width in connecting NAND chips.
|
|
- nb_update tool in fsl_nfc driver rewritten to write FCB, BBT, and
image to NAND.
- vybrid_nand board config added.
- NAND read commands added to DCD that force NFC controller to read
NAND page twice to prevent NFC hang.
|
|
We must enable the external 32kHz oscillator in order to work
around a known clock drift issue with the internal 32kHz oscillator.
This fixes the Linux kernel system clock drift.
Signed-off-by: Anthony Huereca <B04178@freescale.com>
Signed-off-by: Jiri Kotzian <B36968@freescale.com>
Signed-off-by: Justin Waters <justin.waters@timesys.com>
|
|
When enable the hardware ecc in kernel, there are crc errors
for JFFS2 filesystem after write to the filesystem.
Signed-off-by: Jason Jin <Jason.jin@freescale.com>
|
|
Signed-off-by: Jason Jin <Jason.jin@freescale.com>
|
|
Signed-off-by: TsiChung Liew <tsicliew@gmail.com>
|
|
Signed-off-by: TsiChung Liew <tsicliew@gmail.com>
Signed-off-by: Jason Jin <Jason.jin@freescale.com>
|
|
On some platform, such as vybrid, there is no scr register,
but the dis-order excution may wrongly excute the register write.
The barrier used to prevent this.
Signed-off-by: Jason Jin <Jason.jin@freescale.com>
|
|
Signed-off-by: TsiChung Liew <tsicliew@gmail.com>
|
|
Signed-off-by: TsiChung Liew <tsicliew@gmail.com>
|
|
Signed-off-by: TsiChung Liew <tsicliew@gmail.com>
|
|
Signed-off-by: TsiChung Liew <tsicliew@gmail.com>
|
|
Without the fix, flash_write_cfibuffer will terminate the erased
status check once an all-0xFF word has been found instead of
continuing the erased status check utill the first non-0xFF word.
Signed-off-by: Tao Hou <hotforest@gmail.com>
Cc: Stefan Roese <sr@denx.de>
Signed-off-by: Stefan Roese <sr@denx.de>
|
|
This patch adds FAT and ext2 command support for marvell gplugD
Signed-off-by: Ajay Bhargav <ajay.bhargav@einfochips.com>
|
|
This patch adds support for USB commands and USB storage device for
Marvell gplugD
Signed-off-by: Ajay Bhargav <ajay.bhargav@einfochips.com>
|
|
This patch adds support for USB EHCI driver for Armada100 SOCs.
Signed-off-by: Ajay Bhargav <ajay.bhargav@einfochips.com>
|
|
This patch adds USB host controller's UTMI PHY interface driver for
Armada100 SOCs.
Signed-off-by: Ajay Bhargav <ajay.bhargav@einfochips.com>
|
|
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
The dev->req_config flag was indicating that the forwarded
request needs to perform the usb gadget delayed status.
This is however not needed anymore, so it can be removed.
Signed-off-by: Lukasz Majewski <l.majewski@samsung.com>
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
Cc: Marek Vasut <marex@denx.de>
|
|
While receiving packets from FIFO sometimes the buffer provided was
nonaligned. Fix this by taking a temporary aligned buffer and then
copying the content to nonaligned buffer.
Signed-off-by: Shiraz Hashim <shiraz.hashim@st.com>
Signed-off-by: Amit Virdi <amit.virdi@st.com>
|
|
Signed-off-by: Amit Virdi <amit.virdi@st.com>
|
|
This patch adds the support for usb device high speed for designware peripheral.
Signed-off-by: Vipin Kumar <vipin.kumar@st.com>
Signed-off-by: Amit Virdi <amit.virdi@st.com>
|
|
This patch fixes a few bugs in USB device controller driver.
The fixes are as follows
1. Adding error condition checks eg. NULL return
2. Endpoint other than endpoint 0 (control endpoint) are initialized
only if usb state machine reaches STATE_ADDRESSED or above
3. Zero length packet handling corrected
4. Dead code removed
5. Bulk out endpoint returns after servicing 1 interrupt and returns
back to service if more interrupts are pending
Signed-off-by: Vipin Kumar <vipin.kumar@st.com>
Signed-off-by: Amit Virdi <amit.virdi@st.com>
Acked-by: Marek Vasut <marex@denx.de>
|
|
The earlier usb device controller driver was specific to spear platforms. This
patch implements the usb device controller driver as a generic controller which
can be reused by other platforms using this peripheral.
Signed-off-by: Vipin Kumar <vipin.kumar@st.com>
Signed-off-by: Amit Virdi <amit.virdi@st.com>
Acked-by: Marek Vasut <marex@denx.de>
|
|
Common code has a mdelay() func, so use that instead of the usb-specific
wait_ms() func. This also fixes the build errors:
ohci-hcd.c: In function 'submit_common_msg':
/usr/local/src/u-boot/blackfin/include/usb.h:202:44: sorry, unimplemented: inlining failed in call to 'wait_ms': function body not available
ohci-hcd.c:1519:9: sorry, unimplemented: called from here
/usr/local/src/u-boot/blackfin/include/usb.h:202:44: sorry, unimplemented: inlining failed in call to 'wait_ms': function body not available
ohci-hcd.c:1816:10: sorry, unimplemented: called from here
/usr/local/src/u-boot/blackfin/include/usb.h:202:44: sorry, unimplemented: inlining failed in call to 'wait_ms': function body not available
ohci-hcd.c:1827:10: sorry, unimplemented: called from here
/usr/local/src/u-boot/blackfin/include/usb.h:202:44: sorry, unimplemented: inlining failed in call to 'wait_ms': function body not available
ohci-hcd.c:1844:10: sorry, unimplemented: called from here
/usr/local/src/u-boot/blackfin/include/usb.h:202:44: sorry, unimplemented: inlining failed in call to 'wait_ms': function body not available
ohci-hcd.c:1563:11: sorry, unimplemented: called from here
/usr/local/src/u-boot/blackfin/include/usb.h:202:44: sorry, unimplemented: inlining failed in call to 'wait_ms': function body not available
ohci-hcd.c:1583:9: sorry, unimplemented: called from here
make[1]: *** [ohci-hcd.o] Error 1
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Acked-by: Marek Vasut <marex@denx.de>
|
|
musb_hcd.c: In function 'musb_submit_rh_msg':
musb_hcd.c:827:2: warning: format '%d' expects type 'int',
but argument 3 has type 'long unsigned int'
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
Add calls to bootstage before and after relocation, and just
before jumping to the OS.
The idea here is you can call bootstage_report() to get a report.
Additionally, if you define CONFIG_BOOTSTAGE_REPORT then a report is
printed automatically by U-Boot just before jumping to the kernel.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
|
This inserts bootstage calls into tftp, usb start and bootm. We
could go further, but this is a reasonable start to illustrate
the concept.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
|
This defines the basics of a new boot time measurement feature. This allows
logging of very accurate time measurements as the boot proceeds, by using
an available microsecond counter.
To enable the feature, define CONFIG_BOOTSTAGE in your board config file.
Also available is CONFIG_BOOTSTAGE_REPORT which will cause a report to be
printed just before handing off to the OS.
Most IDs are not named at this stage. For that I would first like to
renumber them all.
Timer summary in microseconds:
Mark Elapsed Stage
0 0 reset
205,000 205,000 board_init_f
6,053,000 5,848,000 bootm_start
6,053,000 0 id=1
6,058,000 5,000 id=101
6,058,000 0 id=100
6,061,000 3,000 id=103
6,064,000 3,000 id=104
6,093,000 29,000 id=107
6,093,000 0 id=106
6,093,000 0 id=105
6,093,000 0 id=108
7,089,000 996,000 id=7
7,089,000 0 id=15
7,089,000 0 id=8
7,097,000 8,000 start_kernel
Signed-off-by: Simon Glass <sjg@chromium.org>
|
|
These calls should not be made directly any more, since bootstage
will call the show_boot_...() functions as needed.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
|
Define timer_get_boot_us() which returns the number of microseconds
since boot. If undefined then we use get_timer() * 1000.
We can fit this in a 32-bit register which keeps everyone happy on
the efficiency side. It will wrap around after about an hour. If we
are still looking at it after an hour then we had better not be
timing the boot.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
|
This changes over all the FIT image progress numbers to use enums
from bootstage.h.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
|
This changes over the network-related progress numbers to use enums
from bootstage.h.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
|
This changes over the NAND progress numbers to use enums from
bootstage.h.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
