> +result int the following files:
"int the" -> "in the"
> +The NXM i.MX8MQ EVK Evaluation Board has has two switches responsible
"has has" -> "has"
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/bar
Simon Aittamaa writes:
> I think it was metadata_csum and 64bit...
You're right.
My SDCard was formatted months ago, I only used rsync for the updates.
But the eMMC was formatted afresh by a script from me. I found out with
the feature command "debugfs" that the partitions have different
featur
Hi,
i just noticed that Barebox 2017.08.0 has trouble with one of my ext4
partitions. My i.mX6q device has both SD-Card and eMMC. Normally I boot
from SD-Card, and then from there I use normal "fdisk" / "mkfs.ext4 -F
-j -L $label /dev/$dev" to create the ext4 partitions. Then I mount this
and rsyn
Guillermo Rodriguez Garcia writes:
> With defaultenv-2 the "board configuration" is scattered through a
> number of tiny files, some of which contain just a single value (see
> for example nv/autoboot_timeout or nv/user). I find this more
> difficult to manage -- you need to edit a lot of tiny fi
> shc@shc /home/git/barebox-github $ git status
> На ветке imx51
> Неотслеживаемые файлы:
> (используйте «git add <файл>…», чтобы добавить в то, что будет
> включено в коммит)
export LC_ALL=C; git status
... for those people that aren't as fluent in russian as you :-)
I'm unsure if an "fbtest" command will be helpful.
Why don't you expose the various primitives (lines, circles, lines) with
some commands? Then people could use this in their boot scripts,
including the equivalent of an fbtest program.
___
barebox mail
> +config 2D_PRIMITIVES
> + bool
> +
Why no help text? With help text, it will be discoverable in "make
xconfig".
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
Hi,
is it rectanges or circles? :-)
> Subject: Re: [PATCH 1/3] GUI: Add a function to draw solid rectangles
^^
> Add a routine implementing midpoint circle algorithm
___
barebox mail
> Hi, is barebox now supports load images from usb disk?
better-> Hi, does barebox now support load images from USB?
Yes, this is supported. At least for my hardware (i.MX6).
Basically you first need to detect the USB stick. After this you mount
it and specify the path to vmlinuz, initrd, dtb
> Does this work reliably? Is there finally a patch upstream that creates
> fixed numbers for MMC/SD block devices?
I have a *hack* that in my kernel that names the SD-Card to "sdblk0" and
my eMMC to "mmcblk0". That that is completely unacceptable for upstream,
I never even tried it. :-)
Index:
Guillermo Rodriguez Garcia writes:
> Can anyone provide any hints on why this is
> happening or how to fix it ?
I guess this is probably because your terminal emulation doesn't match
what barebox assume.
I personally connect from Linux via the serial line with kermit to my
target. Kermit has
Alexander Aring writes:
> do you know why memtester from Linux found issues?
No, I actually didn't even look into the source code.
> I saw some people which use memtester under Linux and randomly
> "MTD/filesystem broken" messages blobs out while running memtester. I would
> guess that the memte
> USB Host-A has to be tested, but if I type:
>
>>> usb
>> USB: scanning bus for devices...
>> Bus 001 Device 001: ID : EHCI Host Controller
>> 1 USB Device(s) found
>
> so I can suppose the host controller is working.
I'm unsure if that is correct. When you see the USB IDs of some
connect
Philippe Leduc writes:
> Note: I am using mkimage to create bootable image of a real-time OS
> (PikeOS). There is no initrd or dtc at this step for now: I guess it
> is like loading an old Linux kernel without userspace.
So if you don't have an initrd, do you need uImage at all? You can boot
a b
> Note that splash utility continue to freeze the board.
I'm on an older Barebox (2015.12.0) and here splash works. I do
something like this in my env/bin/init:
splash -x 550 -y 500 -b 0xff /env/logo.png
pwm_0208.period_ns=20
pwm_0208.duty_ns=16
Sascha Hauer writes:
Hi,
> +config CMD_BOOTM_FITIMAGE
> + bool
> + prompt "FIT image support"
> + select FITIMAGE
> + depends on CMD_BOOTM && ARM
> + help
> + Support using FIT Images. Have a look at the u-boot source
> + tree in the "doc/uImage.FIT" folder for mor
Hi Sascha,
I first applied your 3 patches to 2015.09.0 with my old device tree. I
applied your suggest device tree change, now my device tree looks like this:
/ {
...
panel: panel {
compatible = "ampire,am800480r3tmqwa1h", "simple-panel";
/* enable-gpios = <&gpio2 5 GPIO_A
Hi,
on my i.MX6Q device barebox 2015-08.0 worked and I had an output on the splash
screen, both in Barebox and later in Linux (there with CONFIG_STAGING,
CONFIG_DRM_IMX,
DRM_IMX_FB_HELPER, DRM_IMX_LDB, DRM_IMX_IPUV3).
This stopped with 2015-09.0. I even get a null-pointer exception:
Barebox:
2015-07-29 9:47 GMT+02:00 Sascha Hauer :
> + * imx6_esdhc_start_image - Load and start an image from USDHC controller
> + * @instance: The USDHC controller instance (0..4)
> + *
> + * This uses imx6_esdhc_load_image() to load an image from SPI NOR flash.
Hmm, either it's from USDHC or from SPI-NOR
Hmm, this transparent background worked for me using the "inkscape -z
-e ..." method.
What setting do you background-color in File -> Document Properties
(near the top)? The Alpha-Channel must be set to 0 there.
I have attached my sample files.
Blah
__
Imagemagick (and therefore also probably /Graphicsmagic) allows this
from the command line:
convert -setTheOutputSizeOfThePng 1024x1024 test.svg test.png
And Inkscape (my SVG tool of choice) as well:
inkscape -z -e test.png -w 1024 -h 1024 test.svg
Source:
http://stackoverflow.com/questions/9
Better make a Yocto patch. Not everyone compiles Barebox with a "build
environment".
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
Look at barebox/arch/arm/Makefile. Around line 47 you see
"-msoft-float" specified to both CPPFLAGS and AFLAGS. So specifying
"CC=-msoft-hard" would bites with this.
Does compiling Barebox outside of Yocto work? E.g. something like:
make ARCH=arm
CROSS_COMPILE=/home/schurig/d/mkarm/gcc-linaro-a
You better ask in some Yocto-specific mailing list, this isn't really
the problem of Barebox anymore. :-) The soft-float option might come
from one of your inherited configuration files.
Soft-Float is definitely not optimal for the i.MX6, because this one
has FPU commands.
_
Nice logo and docs!
:-)
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
Antony,
that git has such a function doesn't mean that it is usable in any git
project. I too, like Jean-Christophe, that a style issue shouldn't be
named as a fix,
You could always do "git commit --amend" to change the message so that
it actually describes what happens.
Sascha,
AFAIK he implemented two patches from Torvald's linux kernel git tree:
* af958a38a60c7ca3d8a39c918c1baa2ff7b6b233 removes a broken
check-for-integer-overflow method
* 72cf90124e87d975d0b2114d930808c58b4c05e4 add's a new
make-sure-integers-dont-overflow logic, which is also marked as "put
Teresa,
your commit text doesn't seem to be accurate:
> This ports commit 72cf90124e87d975d0b from mainline kernel to the
... and ...
> -#define HAVE_IP(t, x) \
> - (((size_t)(ip_end - ip) >= (size_t)(t + x)) && \
> -(((t + x) >= t) && ((t + x) >
Hmm, you define the function in your patch, but where is it called?
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
> but this doesn't explain a build failure
The build failure was
LD barebox
drivers/built-in.o: In function `of_add_memory':
/home/schurig/d/mkarm/barebox/drivers/of/base.c:1716: undefined
reference to `of_add_memory_bank'
collect2: error: ld returned 1 exit status
make: *** [barebox] Erro
...
Signed-off-by: Holger Schurig
---
commands/memset.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/commands/memset.c b/commands/memset.c
index f869306..4afe404 100644
--- a/commands/memset.c
+++ b/commands/memset.c
@@ -39,7 +39,6 @@ static int
Okay, another post, with less heat.
I asked you specifically if a proposed solution would be ok. You
didn't answer at all. That proposed solution would still not "work"
(it won't add a memory bank, because AFAIK in sandbox there are no
memory banks at all, it just uses the hosts memory). It might
I don't convince you. Eat your own dog foot then. Ignore my patch.
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
There are no memory banks in the sandbox, so adding a working
of_add_memory_bank? How should that work? Or do you mean adding a
dummy of_add_memory_bank() to arch/sandbox/os/board.c?
> his adds ifdeffery (which everyone hates) just for the sake of a static
> checker
You probably never have run
From: Holger Schurig
It won't compile currently anyway.
---
common/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/common/Kconfig b/common/Kconfig
index 469a5d7..dabb7ef 100644
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -650,6 +650,7 @@ config BAREBOXENV_TARGET
c
From: Holger Schurig
Signed-off-by: Holger Schurig
---
commands/lspci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/commands/lspci.c b/commands/lspci.c
index c00b57f..fdf0269 100644
--- a/commands/lspci.c
+++ b/commands/lspci.c
@@ -46,7 +46,7 @@ static int do_lspci(int
From: Holger Schurig
Compiling the tree with allyesconfig is helpful because different
compilers (gcc, clang) or static checkers (e.g. clang's scan-build)
can then process and check more code.
This patch introduces two new configuration symbols that Kconfig files
can depend on. That way,
From: Holger Schurig
I want to use different compilers and static checkers (e.g. clang's
scan-build) on Barebox. As a preparatory step I want to maximize code
coverage in an non-crosscompilation environment.
This patch set prepares the tree so that "make ARCH=sandbox allyesconfig&qu
From: Holger Schurig
This are some minor patches to the documention.
Holger Schurig (5):
Documentation: remove "all all" in help's help text.
Documentation: lowercase help short texts
Documentation: only write changed *.rst files
Documentation: change gener
From: Holger Schurig
... so that it looks a bit nicer in the HTML generated docs.
Signed-off-by: Holger Schurig
---
commands/dfu.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/commands/dfu.c b/commands/dfu.c
index 3546252..7f78f3b 100644
--- a/commands
From: Holger Schurig
Signed-off-by: Holger Schurig
---
commands/help.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/commands/help.c b/commands/help.c
index 9c33807..8985335 100644
--- a/commands/help.c
+++ b/commands/help.c
@@ -128,7 +128,7 @@ static int do_help(int argc
From: Holger Schurig
Documentation/gen_commands.py use to re-write all auto-generated *.rst
file, changed or not. That in turn didn't work well with the internal
cache of the Sphinx documentation generator.
By comparing the SHA1 hash of the newly generated *.rst with the
current sha1 file
From: Holger Schurig
The goal of "make ARCH=sandbox allyesconfig && make all" is not to
generate a sensible barebox that you'd use. The goal is to create
as much code coverage as possible, so that you see compiler warnings
are can send barebox throught a static checker.
From: Holger Schurig
Someone
loadx (load binary file over serial line (X-Modem))
looked more silly than
loadx - load binary file over serial line (X-Modem)
Signed-off-by: Holger Schurig
---
Documentation/gen_commands.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
> issue other lowlevel commands to the bootloader. This adds a
> fastboot implementation based on the U-Boot fatboot code.
Is "fatboot" a type? :-)
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
> * For NAND support it is important to enable *CONFIG_BUS_OMAP_GPMC*
If this is something that is mandatory for the board, maybe the board
should then select it in the Kconfig?
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead
I'd prefer a more logical format (and that is also in the help).
However, in this case I wouldn't name the command "hwclock", but maybe
"setclock".
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
> Is our new (and yet-to-be-uploaded-to-the-net)
> Documentation prominent enough to drop the usage from Kconfig?
I don't think so. I cannot see that someone has xconfig option, and at
the same time the just alphebetically sorted new html documentation
... that's cumbersome, isn't it?
__
> I tend to agree here. When Holger sent these patches recently I was very
> pleased that he has put some love into the Kconfig files. Bit indeed it
> is very hard (and unnecessary) work to keep them in sync. Holger, what's
> your take on this? Is our new (and yet-to-be-uploaded-to-the-net)
> Docum
> Advantage
> - maybe avoid some bad connections (never expired by using sd cards)
This is the k.o. criteria in the company I work for SDCARDs. The
devices run in high vibration / shock targets (e.g. mining), and you
really wouldn't want to have an SDCARD there. You, you could probably
glue the S
Then the help is wrong, I use successfully a small PNG file.
splash -x 550 -y 500 -b 0xff /env/logo.png
$ file logo.png
file.png: PNG image data, 194 x 52, 8-bit/color RGB, non-interlaced
___
barebox mailing list
barebox@lists.infradead.org
http
Oh, please bear with us germans, indians, italians and whoever we are
with our limited pidgin-english knowledge.
No, to turn it the other way around: it's great that a native-english
speaker with knowledge and taste of the language goes over the
documentation.
And at least it's now called "device
> I don't think that the Kconfig entries need to contain the full command
> documentation.
Probably not.
Currently, too many Kconfig options don't have help texts. When I was
new to Barebox, I was puzzled about wether to select an option or not.
Having the complete docs (manually done or auto-gen
t;
Reported-by: Willy Tarreau
Signed-off-by: Holger Schurig
---
lib/lz4/lz4_decompress.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/lib/lz4/lz4_decompress.c b/lib/lz4/lz4_decompress.c
index 75cf08b..9f7bf17 100644
--- a/lib/lz4/lz4_decompress.c
+++ b/lib/lz4/lz4
Tested-by: "Don A. Bailey"
Signed-off-by: Holger Schurig
---
lib/lzo/lzo1x_decompress_safe.c | 64 +++--
1 file changed, 42 insertions(+), 22 deletions(-)
diff --git a/lib/lzo/lzo1x_decompress_safe.c b/lib/lzo/lzo1x_decompress_safe.c
index de795a3..48be
-by: "Don A. Bailey"
Signed-off-by: Holger Schurig
---
lib/lz4/lz4_decompress.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/lz4/lz4_decompress.c b/lib/lz4/lz4_decompress.c
index 8e64ce6..75cf08b 100644
--- a/lib/lz4/lz4_decompress.c
+++ b/lib/lz4/lz4_decompress.c
@@ -
The Kconfig help entries (the source of the generated command
reference) have been written before python-sphinx have been selected.
So basically we need to go over all of them and make sure that they
render correctly. From my point of view, it doesn't harm if you see
raw ReST formatting while insi
While is not
strictly needed, many people use menu/00-foo menu/10-bar menu/20-barf
to sort their menu entries. So select it out of convenience.
Signed-off-by: Holger Schurig
---
v2: just changed the commit text
common/Kconfig |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
menu/10-bar menu/20-barf to sort
their menu entries.
Signed-off-by: Holger Schurig
---
common/Kconfig |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/common/Kconfig b/common/Kconfig
index 1afee93..bba7f15 100644
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -61,6
Rolf, do you use git? Have you tried git sendemail?
This connects directly via SMTP to your internet provider and thus
makes sure that everything is smooth.
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinf
I don't have a clue if that is the "best" toolchain, but I'm using this:
#
## Toolchain
#
# http://www.linaro.org/downloads/#008
GCC_LINARO_FILE
I found a Sphinx cheat sheet:
http://openalea.gforge.inria.fr/doc/openalea/doc/_build/html/source/sphinx/rest_syntax.html
(where you have all the important things on just one page).
So you can convert "This is @b foo bar" to "This is **foo** bar".
___
b
Oh, that's interesting. Because sphinx-build can only be taught about
one sourcedir. But in the srctree != objtree case we have two source
dirs: the in srctree/Documentation with the provided *.rst files, and
the objtree/Documentation/commands, with those files that
@$(srctree)/Documentation/ge
The doc branch deleted all of the *.dox files. And it will eventually
be merged into master and/or next. So I see not much point into
working on the *.dox files anymore. They are basically end-of-life.
Instead, you can either do doc-related work in the origin/doc branch,
or merge that branch into
Yes, normally I have it off. Only after the booting problem I turned it on.
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
Note that I used "Appendix: " as text, because it looks like
python-sphinx doesn't know about appendices.
Signed-off-by: Holger Schurig
---
Documentation/user/system-setup.rst |4 ++--
Documentation/user/user-manual.rst |2 +-
2 files changed, 3 insertions(+), 3 del
Also make this download chapter note the next branch.
Signed-off-by: Holger Schurig
---
Documentation/download.rst | 16
Documentation/index.rst|1 -
Documentation/user/barebox.rst |7 ++-
3 files changed, 6 insertions(+), 18 deletions(-)
delete mode
I kept however the one example that directly demos the bootup on an
Efika board.
---
Documentation/user/driver-model.rst | 10 +-
Documentation/user/networking.rst |2 +-
Documentation/user/updating.rst |2 +-
Documentation/user/variables.rst|2 +-
4 files changed,
Signed-off-by: Holger Schurig
---
Documentation/boards/imx/Phytec-phyCORE-i.MX31.rst |2 +-
Documentation/boards/mxs/Chumby-Falconwing.rst |2 +-
Documentation/boards/mxs/Freescale-i.MX23-evk.rst |2 +-
Documentation/boards/mxs/KaRo-TX28.rst |4
Lines over 120 are just too long :-)
Signed-off-by: Holger Schurig
---
Documentation/boards/imx/Phytec-phyCORE-i.MX31.rst |9 +---
Documentation/boards/mxs/Chumby-Falconwing.rst | 11 +++---
Documentation/boards/mxs/KaRo-TX28.rst |3 ++-
Documentation/boards
Signed-off-by: Holger Schurig
---
Documentation/user/driver-model.rst |2 ++
Documentation/user/variables.rst|7 +--
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/Documentation/user/driver-model.rst
b/Documentation/user/driver-model.rst
index ab7d292..f4b3bb9
Signed-off-by: Holger Schurig
---
Documentation/user/user-manual.rst |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/user/user-manual.rst
b/Documentation/user/user-manual.rst
index aa6c083..0eac0aa 100644
--- a/Documentation/user/user-manual.rst
+++ b
Signed-off-by: Holger Schurig
---
Documentation/user/hush.rst |8
1 file changed, 8 insertions(+)
diff --git a/Documentation/user/hush.rst b/Documentation/user/hush.rst
index 2a0e630..ba4f062 100644
--- a/Documentation/user/hush.rst
+++ b/Documentation/user/hush.rst
@@ -50,3 +50,11
Signed-off-by: Holger Schurig
---
Documentation/filesystems/ramfs.rst |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/ramfs.rst
b/Documentation/filesystems/ramfs.rst
index c2e1e83..2921a35 100644
--- a/Documentation/filesystems/ramfs.rst
+++ b
Signed-off-by: Holger Schurig
---
Documentation/user/barebox.rst |3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/user/barebox.rst b/Documentation/user/barebox.rst
index bab0260..70bdedc 100644
--- a/Documentation/user/barebox.rst
+++ b/Documentation/user/barebox.rst
Signed-off-by: Holger Schurig
---
Documentation/boards/omap.rst|4 ++--
Documentation/commands.rst |4 ++--
Documentation/devicetree/index.rst |2 +-
Documentation/filesystems.rst|2 +-
Documentation/filesystems/ramfs.rst |2 +-
Documentation/user
start with
"barebox" anymore. A lower-case starting heading is (in my eyes!) just
ugly, and if it isn't allowed to capitalize barebox than one can still
change the headline :-) Just for the chapter "barebox" (getting,
configuration, compiling) I haven't found a better name
Signed-off-by: Holger Schurig
---
.gitignore |2 ++
1 file changed, 2 insertions(+)
diff --git a/.gitignore b/.gitignore
index 28f319a..135fdeb 100644
--- a/.gitignore
+++ b/.gitignore
@@ -67,6 +67,8 @@ include/generated
# Generated files
Doxyfile.version
+Documentation/commands/*.rst
> oh, sorry, i missed that doc *branch*, my fault.
It's totally new ... and awesome (compared to the old docs).
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
Good idea. In addition to my board, the Sabre-Lite board also produces
this warning, even twice.
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
Hmm, this is really weird.
On my device, I have a WinCE image on a MMC card. When I insert this
MMC card, the hardware boots from it and I see the output of the EBOOT
on the serial port. So I know that the hardware can boot from SDCARD
(e.g. BOOTCFG setup etc). If I remove the card, then the CPU i
Hmm, I have removed the imx6_init_lowlevel() from my (out-of-tree)
board.c file. Still I get this warning:
__request_region: 0x1000:0x4fff conflicts with 0x1000:0x4fff
Could this be related to your patchset? In the log below, the text "
ahs2_postcore_init, after barebox_set_hostn
> No, we would like to clearly separate user docs
But still it is unfortunate that two "Getting Barebox" chapters are
there at all, and that they are very near to each.
Also, I think that (necessarily!) the design desicions are now mostly
in the user manual, e.g. device parameters. In the non-use
Hi all,
In the Freescale i.MX6Q Reference manual they say in "8. System Boot"
near the end of "8.5.3.1 Expansion Device eFUSE configuration" that
the processor can load from SDCARD, but only up to 32 MB.
Did any one of you succeeded in booting barebox from SDCARD, maybe
with a trampoline code? O
Oh, and I just noticed that two chapters "Getting barebox" are contained:
1. Getting barebox
3.1. Getting barebox
I'd also think that long-term the "user manual" thingy inside the
documention could vanish. Everything could/should/is the user manual,
or?
__
Your patch alone isn't all that's needed, the definition must still be
uncommented. Otherwise we'll get:
drivers/of/base.c:1700:5: error: redefinition of 'of_add_memory'
include/of.h:233:50: note: previous definition of 'of_add_memory' was here
___
bare
Some random annotations. Please comment, after feedback I'll provide a
bunch of patches for this. I don't do the patches right away, because
you may still work currently in that area, so it would only produce
conflicts.
User manuel "2. System setup" should be in an appendix. Nothing here
is reall
Hi,
nice !
I merged remotes/origin/doc into my local checkout of
remotes/origin/next and did "make docs". I got one warning:
schurig@laptop:~/d/mkarm/barebox$ make docs
Making output directory...
Running Sphinx v1.1.2
loading pickled environment... not yet created
building [html]: targets for 2
ot;make ARCH=sandbox" works and compiles warning free, at least
with Debian's gcc-4.6.
Holger Schurig (4):
commands: include missing header
sandbox: only access of_add_memory_bank if it's defined
sandbox: add bit manipulation stuff
sandbox: allow "make ARCH=sandbox allyescon
When compiled for ARCH=sandbox, we get a compiler warning
if we don't include the needed header file as well.
Signed-off-by: Holger Schurig
---
commands/linux_exec.c |1 +
1 file changed, 1 insertion(+)
diff --git a/commands/linux_exec.c b/commands/linux_exec.c
index 741168a..59
rking where a cache or DMA
implementation exists can be opted out.
Signed-off-by: Holger Schurig
---
common/Kconfig | 21 +
drivers/ata/Kconfig |1 +
drivers/input/Kconfig|2 +-
drivers/net/Kconfig |4
dr
... and it's defined only when CONFIG_OFTREE_MEM_GENERIC is on.
Signed-off-by: Holger Schurig
---
drivers/of/base.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/of/base.c b/drivers/of/base.c
index c440a69..818d76e 100644
--- a/drivers/of/base.c
+++ b/drivers/of/b
The functions are already in the sandbox, just the #defines are
missing.
Signed-off-by: Holger Schurig
---
arch/sandbox/include/asm/bitops.h |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/sandbox/include/asm/bitops.h
b/arch/sandbox/include/asm/bitops.h
index 94646d4
On my i.MX6 I have CONFIG_CONSOLE_FULL and CONSOLE_ACTIVATE_NONE
defined. But still my serial is automatically activated as a console.
barebox:/ devinfo cs0
Bus: platform
Parameters:
baudrate: 115200
active: ioe
I'd rather active the serial port as a console only if a key is
pressed during po
I just noticed that simplefb wouldn't work with i.MX6 anyway, even if
I adapt it.
When I setup the framebuffer from barebox and display a splash and
then boot into Linux, then my framebuffer vanishes. Even when I don't
have simplefb or ipu enabled.
I think (!) the reason is the clock framework.Th
Seems like "ls -l" is right, but "devinfo" is wrong:
barebox:/ ls -l /dev/m25p0
crw--- 67108864 /dev/m25p0
barebox:/ devinfo m25p0
Parameters:
size: 5468012149590870304
erasesize: 4096
writesize: 1
oobsize: 0
barebox:/ of_dump /soc/aips-bus@0200/spba-bus@0200/ecspi@0201
e
> My preferred solution is to be fast enough in the bootloader
> and show a splash screen under Linux only.
Hmm, I'd like to not do that. Splash screen from Linux usually means
that I need an initrd. And an initrd is seldom needed on an embedded
device (i.e. no complicated RAID or DM setup). And i
Whaaa, it never occured to me that I have to enable the framebuffer as
well... thanks, now it works.
As for simplefb, I removed that. I thought that this sets up a
framebuffer in the bootloader, which when Linux' framebuffer driver
takes over, without reprogramm or screen flicker. However, it s
Wouldn't it be better if barebox's shell gets the "alias" command?
This would solve a problem like this, and we also could get rid of one
of "edit"/"sedit" commands ...
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailm
Hi, I'm a bit puzzled. I compiled my barebox with
CONFIG_CMD_SPLASH=y
CONFIG_VIDEO=y
CONFIG_DRIVER_VIDEO_IMX_IPUV3=y
CONFIG_DRIVER_VIDEO_IMX_IPUV3_LVDS=y
CONFIG_DRIVER_VIDEO_SIMPLEFB=y
and some entries in the device tree about it (see below). And when I
boot barebox, I see /dev/fb0.
However, the
1 - 100 of 178 matches
Mail list logo
