The more I look into the I2C drivers, the less convinced I am that
fsl_i2c is where I need to be looking.
Additionally, although Variscite had included the fsl_i2c.h header and
had actually referenced fsl_i2c in some documentation and comments,
the more I dig through their code, it is looking
In a quest to support the new Variscite SOM's EEPROM based DDR
configuration, I am continuing to try to get all the pieces together.
Now that I have the SOM actually booting from IRAM, I am actually
trying to get the "real" DDR configuration values out of the EEPROM on
the SOM.
Which brings me
I have already spoken with Sascha about this a bit, but figured I'd
throw it out here in case anyone had any suggestions.
Specifically, I'm updating the support for the Variscite SOM to handle
the newest version of their SOM -- which now includes an EEPROM that
contains a "DCD-like" script for
I have run into an issue that I wonder if anyone else has seen.
We have our kernel stored in NAND flash and have it partition and have
the nand0.kernel and nand0.kernel.bb entries.
As I understand it, the nand0.kernel.bb entry is the correct one to
use for day to day operations as it handles bad
The following patch updates the DCD table in the Variscite iMX6 SOM to
match the current values being used in the most recent u-Boot
distributed in the Variscite Yocto Dora V4 release. These changes are
needed in order to use the most recent SOM's being shipped by
Variscite (due to changes in the
Due to numerous problems that we have experienced with some USB flash
drives on multiple platforms (e.g. iMX35 and iMX6) a variable startup
delay is being added prior to starting to poll the usb devices for
status information. While current versions of the Linux kernel include
multiple retries on
This patch allows barebox to properly load and display BMP files of
any arbitrary size that are generated by most common image editing
packages (e.g. Microsoft Paint, GIMP, etc). The standard Microsoft BMP
format always packs each line of data to a 32-bit boundary (which
means from 0-3 bytes may
This patch is a simple change to allow directly specifying the device
node with the ubirmvol command.
Originally, the ubirmvol command would have to be similar to this:
ubirmvol ubi0 root
With this patch, you can use a -d option and issue the command like
this instead:
ubirmvol -d
This patch adds an option to the OCOTP file for the iMX6 to retrieve
the CPU serial number directly from the hardware using the
barebox,provide-cpu-serial devicetree entry.
Once retrieved, the CPU serial number is stuffed into the appropriate
ATAG for passing to the Linux kernel.
This
This patch corrects exporting unsigned 64-bit environment variables.
I had left out a signed off line before.
Signed-off-by: Michael Burkey mdburkey at gmail.com
---
--- a/common/env.c
+++ b/common/env.c
@@ -258,7 +258,7 @@
void export_env_ull(const char *name, unsigned long long val)
{
-
function doesn't handle signed values, this means that
any values with the msb set cannot be read back in -- which breaks
some things like passing serial # ATAG's to the kernel.
This simple (one character!) fix solves the problem.
Michael D. Burkey
The first time I sent this I apparently typed a character into the
wrong window before I sent it and didn't notice it.
-
--- a/common/env.c
+++ b/common/env.c
@@ -258,7 +258,7 @@
void export_env_ull(const char *name,
Hi ANdreas,
On Wed, Feb 26, 2014 at 07:30:59AM +0100, andreas.willig at rafi.de wrote:
Hi,
has anyone in the community successfully managed to get Barebox
running out of NAND on i.MX6Q/DL? I cannot find any support for BCB /
FCB in the BB sources and am hitting problems while migrating from
unique
ID information stored either.
Don't you just love having to work around problems caused by the
hardware designers trying to pinch pennies?
Thanks!
Michael Burkey
On 2/7/14, Sascha Hauer s.ha...@pengutronix.de wrote:
On Thu, Feb 06, 2014 at 10:24:43PM -0500, Michael D. Burkey wrote
to use for creating boards to work with their
SOM..
On 2/7/14, Michael D. Burkey mdbur...@gmail.com wrote:
Sascha,
I can probably shed a bit more light on this issue actually, now that
I understand it.
The current code you have in barebox SHOULD work with most properly
designed equipment
Philipp,
I have just checked out the tip release of barebox and have been
playing with your added code for the ASIX88772B (which I find a bit
humorous, as I had just migrated almost EXACTLY the same code myself
from the Linux sources two days ago, before I noticed yours -- I had
even put the read
Sascha,
Well, a bit of good news -- I know what the problem is, and it is
probably one that has actually caused headaches for other people over
the years (probably in the Linux kernel as well).
The problem is one that only shows up with a powered hub which uses
external power switches to feed
Sascha,
I have enabled the USB debugging (and added some additional code as
well). I'm still trying to figure out exactly why it's not detecting
my flash drive without another device being present. One thing that is
weird is that it has to be a non-mass storage device of some kind for
things to
18 matches
Mail list logo
