just tried to build docs on a fully-updated fedora 31 system, and
got:
$ make htmldocs
SPHINX htmldocs --> file:///home/rpjday/uboot/git/doc/output
make[2]: Nothing to be done for 'html'.
Running Sphinx v2.1.2
Extension error:
Could not import extension kerneldoc (exception: cannot import
Various (mostly minor) spelling, grammar and punctuation tweaks for
arch/arm/Kconfig.
Signed-off-by: Robert P. J. Day
---
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index f9dab073ea..36c9c2fecd 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -17,7 +17,7 @@ config
short form: is there an efficient way to add a new vendor and new
zynqmp-based board to the u-boot infrastructure without creating a
whole new vendor directory that (mostly) duplicates what is already
under board/xilinx/?
as i read it, if i configure u-boot for, say, a xilinx zynqmp-based
ZC
ot for the BBB:
http://www.crashcourse.ca/wiki/index.php/U-Boot_on_the_BBB#Building_a_stock_u-boot_for_the_BBB
last time i looked, that recipe worked just fine.
rday
--
================
Robert P. J. Day Ottaw
Signed-off-by: Robert P. J. Day
---
diff --git a/include/config_distro_defaults.h b/include/config_distro_defaults.h
index 5d18a4b..1ecc0bb 100644
--- a/include/config_distro_defaults.h
+++ b/include/config_distro_defaults.h
@@ -10,7 +10,7 @@
/*
* List of all commands and options that when
Signed-off-by: Robert P. J. Day
---
given that the typoes occur in Kconfig help and a comment, the
changes are effectively non-functional.
diff --git a/dts/Kconfig b/dts/Kconfig
index 83ba7a6..5fe63f8 100644
--- a/dts/Kconfig
+++ b/dts/Kconfig
@@ -49,7 +49,7 @@ config DEFAULT_DEVICE_TREE
running "make help" concludes with the claim:
"Execute "make" or "make all" to build all targets marked with [*]"
but i see no make targets marked that way -- i suspect that was just a
copy and paste from the kernel Makefile, yes?
rday
___
U-Boot m
On Wed, 22 Oct 2014, Masahiro Yamada wrote:
>
>
>
>
> On Tue, 21 Oct 2014 16:23:24 -0400 (EDT)
> "Robert P. J. Day" wrote:
>
> >
> > running "make help" concludes with the claim:
> >
> > "Execute "make" or &q
ters. i've never tried u-boot in a QEMU session
before; hence the fairly intro-level request for help.
rday
--
============
Robert P. J. Day Ottawa, Ontario, CANADA
On Mon, 28 Nov 2011, Wolfgang Denk wrote:
> Dear "Robert P. J. Day",
>
> In message you wrote:
> >
> > i'm teaching some embedded linux next week and, while i will have
> > physical boards for the students to play with, i'd also like to
> >
nd
am i just missing something obvious? what should i use for the
kernel console setting? i'm open to suggestions.
rday
--
Robert P. J. Day Ottawa, Ontario, CANAD
On Fri, 2 Dec 2011, Scott Wood wrote:
> On 12/02/2011 05:19 PM, Robert P. J. Day wrote:
> > and, at this point, i would think that all i need to do is:
> >
> > => bootm 40
> > ## Booting image at 0040 ...
> >Image Name: Linux-2.6.37
> >
On Fri, 2 Dec 2011, Scott Wood wrote:
> On 12/02/2011 05:41 PM, Robert P. J. Day wrote:
> > ok, so what's the "make" invocation to get one of those? i'm not a
> > ppc expert so i don't know much about device trees. i tried the
> > followi
rying to do this with u-boot 0.4.0, and that's just the way it is.
sometimes, you just have to work with what you're given, wolfgang.
sorry if that cramps your style.
rday
--
Robert P. J. Day
, it's late so i'll tackle this again tomorrow.
rday
--
========
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter:
t; >
> > rday
>
> What version of uboot do you use? What compiler and it's version do you use?
i'm using the latest "git pull" of u-boot, and:
$ powerpc-unknown-linux-gnu-gcc --version
powerpc-unknown-linux-gnu-gcc (crosstool-NG-1.10.0) 4.4.5
...
i get the
On Sat, 3 Dec 2011, Wolfgang Denk wrote:
> Dear Robert,
>
> In message you wrote:
> >
> > > What version of uboot do you use? What compiler and it's version do you
> > > use?
> >
> > i'm using the latest "git pull" of u-boot, and:
> >
> > $ powerpc-unknown-linux-gnu-gcc --version
> > powerpc-u
On Sat, 3 Dec 2011, Marek Vasut wrote:
> > On Sat, 3 Dec 2011, Wolfgang Denk wrote:
> > > Dear Robert,
> > >
> > > In message you wrote:
> > > > > What version of uboot do you use? What compiler and it's version do
> > > > > you use?
> > > > >
> > > > i'm using the latest "git pull" of u-boot,
On Sat, 3 Dec 2011, Wolfgang Denk wrote:
> Dear Robert,
>
> In message you wrote:
> >
> > > What version of uboot do you use? What compiler and it's version do you
> > > use?
> >
> > i'm using the latest "git pull" of u-boot, and:
> >
> > $ powerpc-unknown-linux-gnu-gcc --version
> > powerpc-u
On Sat, 3 Dec 2011, Anatolij Gustschin wrote:
> Hi Robert,
>
> On Sat, 3 Dec 2011 12:47:47 -0500 (EST)
> "Robert P. J. Day" wrote:
> ...
> > > Top of tree:
> > > -> git describe
> > > v2011.09-1259-g7708d8b
> > > ->
On Sat, 3 Dec 2011, Anatolij Gustschin wrote:
> On Sat, 3 Dec 2011 15:12:44 -0500 (EST)
> "Robert P. J. Day" wrote:
> ...
> > um, my understanding for the need of that script (or its equivalent,
> > which i assume is just to switch to the git 4.2 bran
On Fri, 2 Dec 2011, Scott Wood wrote:
> On 12/02/2011 05:19 PM, Robert P. J. Day wrote:
> > and, at this point, i would think that all i need to do is:
> >
> > => bootm 40
> > ## Booting image at 0040 ...
> >Image Name: Linux-2.6.37
> >
erstand it, i want a
> > cuImage-format file as i used with my lite5200, so i edited the file
>
> No. Now you don't need a cuImage nay more. Just use the DT as I
> showed you in the builkd and boot log I sent before.
ah, gotcha. i'll do that, thanks.
rday
--
=====
bly a good idea to move to the device tree
recipe, that still doesn't explain why i can't use a cuImage file for
my tqm boards. so i'll test the device tree process later today, but
i'm still curious as to why a cuImage format file still fails in this
case when it works just
aterial to work with, and i'm making an effort
to change as little of it as possible if i don't have to, at the
request of the person who gave it to me. and sometimes, political
reasons might trump technical reasons, as much as we don't want them
to.
rday
--
==
s odd -- already noticed some
minor typoes.
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter:
On Sat, 10 Dec 2011, Wolfgang Denk wrote:
> Dear "Robert P. J. Day",
>
> In message you wrote:
> >
> > rather than cast around looking for a solution, i figure i can
> > better invest my time just reading this end to end:
> >
> > http:
On Mon, 4 Mar 2013, Tom Rini wrote:
> On Thu, Feb 28, 2013 at 08:46:15AM -0500, Robert P. J. Day wrote:
>
> > it would seem that in addition to manually setting HOSTCC, a user
> > should also set HOSTSTRIP when building fw_printenv, no? there's no
> > mention of tha
M of output to a mailing
list? what's wrong with pastebin?
rday
--
============
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter:
to get you started, and you can match up
running the commands with the underlying code.
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter:
Make USB help info for "start" subcommand consistent with other USB
subcommands.
Signed-off-by: Robert P. J. Day
---
unless there's something different about the "start" subcommand,
this would seem to make sense for consistency.
diff --git a/common/cmd_usb.c
NGHELP is defined, the symbol
"pci_help_text" is created as the text, but its *usage* just below in
the U_BOOT_CMD macro is *outside* of that preprocessor check. how
would that work if CONFIG_SYS_LONGHELP is undefined? not at my dev
host right this minute so i can't test, but it just loo
On Sat, 26 Jan 2013, Albert ARIBAUD wrote:
> Hi Robert,
>
> On Sat, 26 Jan 2013 06:38:51 -0500 (EST), "Robert P. J. Day"
> wrote:
... snip ...
> > and second, i'm not sure how to read this out of cmd_pci.c:
> >
> > = start
> >
> >
On Sat, 26 Jan 2013, Robert P. J. Day wrote:
>
> Make USB help info for "start" subcommand consistent with other USB
> subcommands.
ACK, never mind, i just remembered that the first character string
of the long help automatically gets the command name prepende
On Sat, 26 Jan 2013, Albert ARIBAUD wrote:
> Hi Robert,
>
> On Sat, 26 Jan 2013 07:11:18 -0500 (EST), "Robert P. J. Day"
> wrote:
>
> > On Sat, 26 Jan 2013, Albert ARIBAUD wrote:
> >
> > > Hi Robert,
> > >
> > > On Sat, 2
Fix a comment in the fw_env.config file, no functional change.
Signed-off-by: Robert P. J. Day
---
diff --git a/tools/env/fw_env.config b/tools/env/fw_env.config
index 8e21d5a..9d3b1a4 100644
--- a/tools/env/fw_env.config
+++ b/tools/env/fw_env.config
@@ -1,4 +1,4 @@
-# Configuration file for
the bootable SD card that came with the kit, it's
based on the arago project so i know i have something that boots to
userspace as a starting point -- always good to know.
--
================
Robert P. J. Day
t comment should read:
# Configuration file for fw_(printenv/setenv) utility.
if it's anything more than just a trivial fix, i'll ask first.
rday
p.s. just edited that page, hope i did it correctly. onward ...
--
=
S += -DCONFIG_SH -D__SH__
^^^
not suggesting they deserve immediate removal, just want to verify
that my understanding is correct and that they're unnecessary.
thanks.
rday
--
================
Robert P. J. Day
same name to have that
single, subtle difference just looks strange.
rday
--
============
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter:
On Fri, 1 Feb 2013, Robert P. J. Day wrote:
> ... the same source file -- AMDLV065D.c -- is in two different
> directories, and they differ slightly:
>
> $ diff board/{altera,psyent}/common/AMDLV065D.c
> 175c175
> < writeb (b, dst);
> ---
> &
ot;version" to that page,
just for fun.
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn:
Tidy up indentation, and use what appears to be the standard of
"unsigned long" rather than "ulong" in u-boot.h files.
Signed-off-by: Robert P. J. Day
---
should be no functional change here, just aesthetics.
diff --git a/arch/arm/include/asm/u-boot.h b/arch/arm/includ
DECLARE_GLOBAL_DATA_PTR;
return gd->main_clk_rate_hz;
}
and based on how gcc optimizes, i'm not convinced that that macro
invocation is going to be in file-global scope, or am i just
forgetting my C scoping rules?
rday
--
===============
be corrected.
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.li
Signed-off-by: Robert P. J. Day
---
based on perusal of entire file as i was reading code. undoubtedly
more of these file-wide proofreads coming if no objections ...
diff --git a/common/cmd_mem.c b/common/cmd_mem.c
index 0f3ffc8..2568c04 100644
--- a/common/cmd_mem.c
+++ b/common/cmd_mem.c
On Sat, 2 Feb 2013, Jeroen Hofstee wrote:
> On 02/02/2013 05:04 PM, Robert P. J. Day wrote:
> > Signed-off-by: Robert P. J. Day
> >
> > ---
> >
> >based on perusal of entire file as i was reading code. undoubtedly
> > more of these file-
Signed-off-by: Robert P. J. Day
---
i'm going to leave the comment format as it is since it matches all
of the other brief comments in that file.
diff --git a/common/cmd_mem.c b/common/cmd_mem.c
index 0f3ffc8..2568c04 100644
--- a/common/cmd_mem.c
+++ b/common/cmd_mem.c
@@ -462,7 +
tic uint dp_last_addr, dp_last_size;
... snip ...
which, as you can see, has a leading blank line but not a following
one. so what's correct? is this written down somewhere?
rday
--
Robert P. J. Day
Signed-off-by: Robert P. J. Day
---
fixing a few simple typoes should not represent this much grief.
diff --git a/common/cmd_mem.c b/common/cmd_mem.c
index 0f3ffc8..d44aa1d 100644
--- a/common/cmd_mem.c
+++ b/common/cmd_mem.c
@@ -462,7 +462,8 @@ static int do_mem_loop(cmd_tbl_t *cmdtp, int
k about that first.
rday
--
============
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://
do_serial_flash,
"Serial flash sub-system",
"probe [bus:]cs - init flash device on given SPI bus and CS")
i'm confused ...
rday
--
================
Robert P. J. Day
Signed-off-by: Robert P. J. Day
---
i think i got this right ... those chunks are just long enough that
comments are useful.
diff --git a/common/cmd_load.c b/common/cmd_load.c
index 2c8dab1..46db962 100644
--- a/common/cmd_load.c
+++ b/common/cmd_load.c
@@ -1064,8 +1064,8 @@ U_BOOT_CMD
mentation of the "reginfo"
command, and the relevant test is already being done in the Makefile:
COBJS-$(CONFIG_CMD_REGINFO) += cmd_reginfo.o
am i understanding that correctly? thanks.
rday
--
==============
/file_reference
not perfect, but it gives me a quick way to know what source files
provide which commands, and under what circumstances.
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
another observation from my weekend perusal of all of the
common/cmd_*.c files is that, despite its "cmd_" filename prefix, the
source file cmd_disk.c doesn't define any actual u-boot commands.
according to what i see as u-boot filename naming conventions, it
shouldn't be named "cmd_*",
Quoting Albert ARIBAUD :
Hi Robert,
On Mon, 04 Feb 2013 07:53:43 -0500, "Robert P. J. Day"
wrote:
another observation from my weekend perusal of all of the
common/cmd_*.c files is that, despite its "cmd_" filename prefix, the
source file cmd_disk.c doesn't
i know i mentioned it this weekend but the only reason i tripped
over that cmd_disk.c thingie is that i built myself a cmd_*.c
reference list, matching source files with defined commands and
any preprocessor conditions that defined them here:
http://www.crashcourse.ca/wiki/index.php/U-Boot_comm
i mentioned this this weekend as well, can someone clarify this?
the source file cmd_df.c looks weird:
U_BOOT_CMD(
sf, 2, 1, do_serial_flash,
"Serial flash sub-system",
"probe [bus:]cs - init flash device on given SPI bus and CS")
so the source fil
Signed-off-by: Robert P. J. Day
---
diff --git a/common/cmd_mtdparts.c b/common/cmd_mtdparts.c
index 06fc171..7398371 100644
--- a/common/cmd_mtdparts.c
+++ b/common/cmd_mtdparts.c
@@ -1422,7 +1422,7 @@ static int delete_partition(const char *id)
return 1
Nothing appears to use or compile cmd_df.c anymore.
Signed-off-by: Robert P. J. Day
---
hope this is the right format for deleting a file.
diff --git a/common/cmd_df.c b/common/cmd_df.c
deleted file mode 100644
index f7e5df3..000
--- a/common/cmd_df.c
+++ /dev/null
@@ -1,36 +0,0
a few basic questions about a board i don't have access to right
this minute but did yesterday and will later today. it's an AM1808
experimenter kit lookalike except that it has (allegedly) had its NOR
flash replaced with 2G of NAND flash, and i want to figure out what i
can add to the c
Quoting Eric Bénard :
Hi Robert,
Le Tue, 05 Feb 2013 08:37:20 -0500,
"Robert P. J. Day" a écrit :
main question -- should flinfo not tell me about my flash? what
might this configuration be missing? i should have access to the
board in an hour or two. thanks.
you can
some time ago, i wrote some simple shell scripts that scanned the
kernel source tree and identified oddities in configuration files --
things like Kconfig variables that were defined but never used, macros
that were being tested but were never set, etc. i just tweaked one of
those script
self-explanatory -- variables that are explicitly defined but are
apparently never used anywhere in the code. amusingly, i had to open
up the matching when i noticed the misspelling at the end. if all of
these are superfluous, i can submit a single patch to remove it all.
i will shut
Quoting Scott Wood :
On 02/05/2013 07:37:20 AM, Robert P. J. Day wrote:
a few basic questions about a board i don't have access to right
this minute but did yesterday and will later today. it's an AM1808
experimenter kit lookalike except that it has (allegedly) had its NOR
flas
27;d use for this situation, and where
that single u-boot image would end up.
rday
--
========
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.
Signed-off-by: Robert P. J. Day
---
diff --git a/tools/env/README b/tools/env/README
index df020e4..1020b57 100644
--- a/tools/env/README
+++ b/tools/env/README
@@ -8,7 +8,7 @@ In order to cross-compile fw_printenv, run
in the root directory of the U-Boot distribution. For example,
make
it would seem that in addition to manually setting HOSTCC, a user
should also set HOSTSTRIP when building fw_printenv, no? there's no
mention of that in the README but the strip operation will certainly
fail without it.
rday
___
U-Boot mailing list
U
t converter and everything was fine. so i'm
still curious about potential problems with minicom and u-boot.
rday
--
================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training
On Wed, 19 Aug 2009, Wolfgang Denk wrote:
> Dear "Robert P. J. Day",
>
> In message you wrote:
> >
> > i purchased a different converter and everything was fine. so i'm
> > still curious about potential problems with minicom and u-boot.
>
&
on 1 (SYSV),
statically linked, not stripped
$
look reasonable. all in all, pretty simple unless someone wants to
point out anything i did wrong. if i screwed up, it's just going on
an SD card so there's little chance of me breaking anything.
rday
--
====
i want to use ELDK 4.2 to cross-compile u-boot for my beagleboard,
can someone verify that it does that properly? thanks.
rday
--
Robert P. J. Day Waterloo, Ontario, CANADA
Linux
ap3 are defined in
terms of OMAP34XX as well and while that may work fine for now, is
there any chance that could cause conflicts down the road?
rday
--
================
Robert P. J. Day Waterloo, Ontario
Bring the directory listing more into line with current content.
Signed-off-by: Robert P. J. Day
---
not meant to be comprehensive, just to get things more up-to-date.
feel free to tweak as you see fit.
diff --git a/README b/README
index 2c77687..1e1bccc 100644
--- a/README
+++ b/README
Explicitly demonstrate an example (BeagleBoard) of what was
added/changed to support a new board.
Signed-off-by: Robert P. J. Day
---
obviously not critical, but it might be useful for readers to see
explicitly what constitutes adding support for a new board, file by
file. your choice to
On Tue, 17 Nov 2009, Dirk Behme wrote:
> Robert P. J. Day wrote:
> > Explicitly demonstrate an example (BeagleBoard) of what was
> > added/changed to support a new board.
> >
> > Signed-off-by: Robert P. J. Day
> >
> > ---
> >
> > obviously
Show the simple end result of adding an example board (BeagleBoard).
Signed-off-by: Robert P. J. Day
---
based on dirk's earlier email, i'm emphasizing that this represents
only the *end result* of adding BeagleBoard support to U-Boot.
anything more involved than that wouldn'
Show the simple end result of adding an example board (BeagleBoard).
Signed-off-by: Robert P. J. Day
---
based on dirk's earlier email, i'm emphasizing that this represents
only the *end result* of adding BeagleBoard support to U-Boot.
anything more involved than that wouldn'
"nandecc" help output should not reproduce the command name, nor have
a trailing newline.
Signed-off-by: Robert P. J. Day
---
compiled, loaded and run to verify correct output.
diff --git a/cpu/arm_cortexa8/omap3/board.c b/cpu/arm_cortexa8/omap3/board.c
index dd2c940..2aa69b3 10
On Tue, 17 Nov 2009, Wolfgang Denk wrote:
> Dear "Robert P. J. Day",
>
> In message you wrote:
> >
> > Show the simple end result of adding an example board (BeagleBoard).
> >
> > Signed-off-by: Robert P. J. Day
>
> This text is sti
confused?
rday
--
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
ming convention of those files, i would
have imagined a file by the name of cmd_pinit.c.
--
============
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web p
Collect object files corresponding to the same CONFIG variable on the
same line for better readability.
Signed-off-by: Robert P. J. Day
---
clearly no *functional* difference but it follows the standard set
out in the rest of the file. compile tested for a beagle, for what
it's
Collect object files corresponding to the same CONFIG variable on the
same line for better readability.
Signed-off-by: Robert P. J. Day
---
clearly no *functional* difference but it follows the standard set
out in the rest of the file. compile tested for a beagle, for what
it's
ver? any reason why
CONFIG_SYS_PROMPT can't be set directly and V_PROMPT ignored/removed?
rday
--
============
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and K
.
Signed-off-by: Robert P. J. Day
---
based on simple visual inspection, i can't see how those tests could
make any difference so they might as well be tossed.
diff --git a/common/cmd_cache.c b/common/cmd_cache.c
index 0dfa336..1202258 100644
--- a/common/cmd_cache.c
+++ b/common/cmd_ca
nneeded
> #ifdef CONFIG_CMD_LICENSE". Could you remove the above chunk from your
> patch and resubmit so as to prevent a conflict when Wolfgang applies
> both patches?
okey dokey, coming right up.
rday
--
===
.
Signed-off-by: Robert P. J. Day
---
revision of earlier patch, dropping change to cmd_license.c since
that's already been submitted.
there *are* at least a couple more files like this but they'll
require slightly different tweaking so i'm doing those separately.
diff --git a/com
Move the CONFIG_CMD_NAND preprocessor test out of common/cmd_nand.c
and into the Makefile for consistency with other commands.
Signed-off-by: Robert P. J. Day
---
AFAICT, this doesn't affect any functionality, right?
diff --git a/common/Makefile b/common/Makefile
index 3781738..b8
Move the preprocessor test of CONFIG_SYS_NO_FLASH out of flash.c and
back to the Makefile, for readability.
Signed-off-by: Robert P. J. Day
---
this one is a little uglier since it adds an "#ifndef" check to the
Makefile, but i still consider this to be more readable since it
On Thu, 19 Nov 2009, Mike Frysinger wrote:
> On Thursday 19 November 2009 12:38:42 Robert P. J. Day wrote:
> > --- a/common/Makefile
> > +++ b/common/Makefile
> > @@ -152,7 +152,9 @@ COBJS-$(CONFIG_VFD) += cmd_vfd.o
> > COBJS-$(CONFIG_DDR_SPD) += ddr_spd.o
&
Make it clear to a reader that the user of OMAP34XX macros in the
(OMAP 3530-based) beagle config file is just fine.
Signed-off-by: Robert P. J. Day
---
i'll let dirk be the judge as to whether this is worth adding, or if
he'd prefer a different phrasing.
diff --git a/inclu
Remove the use of the V_PROMPT macro in a number of config files,
whose only use seems to be to subsequently set the CONFIG_SYS_PROMPT
macro, after which it's never used again.
Signed-off-by: Robert P. J. Day
---
as far as i can tell, there's no compelling reason to hang onto
V_P
On Fri, 20 Nov 2009, M?ns Rullg?rd wrote:
> "Robert P. J. Day" writes:
>
> > Make it clear to a reader that the user of OMAP34XX macros in the
> > (OMAP 3530-based) beagle config file is just fine.
> >
> > Signed-off-by: Robert P. J. Day
> >
>
Make it clear to the reader that, since OMAP 34XX and 35XX are the
same silicon, the BeagleBoard can use the OMAP34XX macros.
Signed-off-by: Robert P. J. Day
---
diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h
index 19a5ec9..59b7edc 100644
--- a/include/configs
use 34XX.
rday
--
====
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.c
ort? what am i
missing?
rday
--
================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter:
On Fri, 20 Nov 2009, Tom wrote:
> Robert P. J. Day wrote:
> > Make it clear to the reader that, since OMAP 34XX and 35XX are the
> > same silicon, the BeagleBoard can use the OMAP34XX macros.
> >
> > Signed-off-by: Robert P. J. Day
> >
> > ---
> >
&g
P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
1 - 100 of 461 matches
Mail list logo
