Hi Heinrich,
On Sun, 31 May 2020 at 09:34, Heinrich Schuchardt wrote:
>
> Hello Simon,
>
> in some drivers we use printk() which is restricted by CONFIG_LOGLEVEL
> and translates to printf().
>
> Shouldn't printk() be translated to log() instead?
>
> CONFIG_LOGL
Hello Simon,
in some drivers we use printk() which is restricted by CONFIG_LOGLEVEL
and translates to printf().
Shouldn't printk() be translated to log() instead?
CONFIG_LOGLEVEL probably should better be renamed to
CONFIG_PRINTK_LOGLEVEL to avoid confusion.
And those different levels like
On Sat, Sep 16, 2017 at 02:10:40PM +0900, Masahiro Yamada wrote:
> When we import code from Linux, with regular re-sync planned, we want
> to use printk() and pr_*(). U-Boot does not support them in a clean
> way. So, people end up with local macros, or compat headers here and
> th
da <yamada.masah...@socionext.com>:
> >> >
> >> > I tested this series with buildman.
> >> >
> >> >
> >> >
> >> > Masahiro Yamada (8):
> >> > stdio.h: move printf() stuff from to
> >> > printk: coll
>> >
>> >
>> >
>> > Masahiro Yamada (8):
>> > stdio.h: move printf() stuff from to
>> > printk: collect printk stuff into with loglevel
>> > support
>> > treewide: replace with error() with pr_err()
>> >
On Wed, Oct 04, 2017 at 02:15:19PM +0900, Masahiro Yamada wrote:
> 2017-09-16 14:10 GMT+09:00 Masahiro Yamada <yamada.masah...@socionext.com>:
> >
> > I tested this series with buildman.
> >
> >
> >
> > Masahiro Yamada (8):
> > stdio.h: move pr
I tested this series with buildman.
Masahiro Yamada (8):
stdio.h: move printf() stuff from to
printk: collect printk stuff into with loglevel
support
treewide: replace with error() with pr_err()
common.h: remove error()
vsprintf.h: include
bug.h: sync BUILD_BUG stuff
When we import code from Linux, with regular re-sync planned, we want
to use printk() and pr_*(). U-Boot does not support them in a clean
way. So, people end up with local macros, or compat headers here and
there, then we occasionally see build errors of definition conflicts.
We have include
on 'phy_info_parse':
w+../drivers/net/mvpp2.c:4751:27: warning: cast to pointer from
integer of different size [-Wint-to-pointer-cast]
02: printk: collect printk stuff into
arm: + colibri_vf openrd_base vf610twr_nand openrd_ultimate
vf610twr openrd_client
-../include/common.h:627:5: note:
buildman is 60% done, and no regression so far.
I will report the full-stat when buildman is complete.
Masahiro Yamada (6):
printk: collect printk stuff into
treewide: replace with error() with pr_err()
common.h: remove error()
vsprintf.h: include
bug.h: sync BUILD_BUG stuff
When we want to print something to the console, we generally include
, then use printf() and friends.
When we import code from Linux, planning to sync it from time to time,
we want to use printk() and pr_*(). U-Boot does not support them in
a clean way. So, people end up with local macros
+++ b/drivers/mtd/nand/atmel_nand.c
@@ -412,7 +412,7 @@ static int pmecc_err_location(struct mtd_info *mtd)
}
if (!timeout) {
- printk(KERN_ERR atmel_nand : Timeout to calculate PMECC error
location\n);
+ dev_err(host-dev, atmel_nand : Timeout
On Tue, 31 Aug 2010 19:18:27 -0500
Paulraj, Sandeep s-paul...@ti.com wrote:
This printk was added recently and results in ugly output on systems
with no NAND:
NAND: nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x00,
Chip ID: 0x00 0 MiB
instead of:
NAND
On Wed, 2010-09-01 at 11:26 -0500, Scott Wood wrote:
On Tue, 31 Aug 2010 19:18:27 -0500
Paulraj, Sandeep s-paul...@ti.com wrote:
This printk was added recently and results in ugly output on systems
with no NAND:
NAND: nand_get_flash_type: unknown NAND device
On Wed, 1 Sep 2010 09:43:17 -0700
Steve Sakoman st...@sakoman.com wrote:
On Wed, 2010-09-01 at 11:26 -0500, Scott Wood wrote:
Hmm, the current use of that seems to be suppressing warnings about
NAND that isn't present at all, not about NAND whose type we don't
recognize.
Well, that is
This printk was added recently and results in ugly output on systems
with no NAND:
NAND: nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x00, Chip
ID: 0x00 0 MiB
instead of:
NAND: 0 MiB
Signed-off-by: Steve Sakoman st...@sakoman.com
---
drivers/mtd/nand/nand_base.c |2 ++
1
This printk was added recently and results in ugly output on systems
with no NAND:
NAND: nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x00,
Chip ID: 0x00 0 MiB
instead of:
NAND: 0 MiB
Scott,
What do you think of this patch?
Signed-off-by: Steve Sakoman st
Hi Magnus,
uImage to. Itried 0x8100 and 0x80008000 and i am still unable
to load the kernel off u-boot.?
Thanks for all the help! I have got linux booting from u-boot. So
it had something to do with one of the device drivers
Doing a post mortem on the printk log buffer pointed me
a post mortem on the printk log buffer pointed me to the problem.
Excellent!
/Magnus
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Magnus,
I tend to load my kernels to 0x8100 and not 0x80008000 but I don't
know if that really matters. Other than that I think 'run bootcmd_net'
should work.
Oops i realized i top posted:( I am re-posting again.
i checked in the kernel code
Hi
2009/5/1 alfred steele alfred.jaq...@gmail.com:
Hi Magnus,
I tend to load my kernels to 0x8100 and not 0x80008000 but I don't
know if that really matters. Other than that I think 'run bootcmd_net'
should work.
Oops i realized i top posted:( I am re-posting again.
i checked in the
Yes, those values are correct. The boot_params address is also in
arch/arm/mach-mx3/mx31pdk.c (mx3_3stack.c if you use Freescale's BSP).
Where do i get the latest version of Freescale BSP? i know this is not
the correct forum...but still
Thanks,
Alfred
Dear alfred steele,
In message 528f13590905010838g1a1dc360gfd5fd4a64e84d...@mail.gmail.com you
wrote:
Where do i get the latest version of Freescale BSP? i know this is not
the correct forum...but still
From Freescale? Try www.freescale.com ...
Best regards,
Wolfgang Denk
--
DENX
--- On Fri, 5/1/09, alfred steele alfred.jaq...@gmail.com wrote:
Where do i get the latest version of Freescale BSP? i know
this is not
the correct forum...but still
--- On Fri, 5/1/09, alfred steele alfred.jaq...@gmail.com wrote:
Where do i get the latest version of Freescale BSP? i know
this is not
the correct forum...but still
(Click on IMX31_PDK_14_LINUX_BSP_R14 )
Thanks Fabio. Do you know what the load address and entry point for
creating a uImage are for the mx31 pdk board and where to load the
uImage to. Itried 0x8100 and 0x80008000 and i am still unable
to load the kernel off u-boot.?
Best Regards,
Alfred
Hi
2009/4/30 alfred steele alfred.jaq...@gmail.com:
Hi Magnus,
The mainline u-boot + my patches from early April does not contain any
driver for the i.MX31 NAND flash controller so that can't autodetect
any flash part at all.
How does it boot out of NAND then? I am getting confused. By
Hi Magnus,
If U-boot had full NAND support for i.MX31, NAND would be detected
somewhere between steps 7 and 8.
Thanks for the elaborate explanation. I did not find any detailed
documentation for the same in the u-boot readme's.
See my explanation above. CONFIG_SKIP* is defined when compiling
Have you got a chance to post the patches to the mainline yet?
No, but as I stated earlier the only merge problem I got was in the
top Makefile and that was easy to fix.
I need more time to post the patches since I'm taking care of some
comments that were posted to Maxim's patches (which I'm
Hi Magnus,
I need more time to post the patches since I'm taking care of some
comments that were posted to Maxim's patches (which I'm using as a
base).
That's fine.
Which linker script gets actually used for the layout in in case of
nand_spl. Is it u-boot-nand.lds or u-boot.lds.?
Thanks.
for booting a linux kernel. WHat could be the
reason that the( md of the printk log does not show up the console
=ttymxc0,115200 correctly.
It looks like its. just ttymxc0,1152 as evident from the memory
dump i had sent ealier in this thread.
=printenv
baudrate=115200
netdev=eth0
uboot=u
is a dump of my U-boot env. Does
it look good enough for booting a linux kernel. WHat could be the
reason that the( md of the printk log does not show up the console
=ttymxc0,115200 correctly.
It looks like its. just ttymxc0,1152 as evident from the memory
dump i had sent ealier
Hi
2009/4/28 alfred steele alfred.jaq...@gmail.com:
Hi Magnus,
But when i tried burning u-boot-nand.bin to the base address and
boot , i get only one line printed on the console which is
U-Boot 2009.01 (Apr 28 2009 - 15:27:19)
If it comes that far it looks like a lot is working. Don't
Hi Alfred,
--- On Tue, 4/28/09, alfred steele alfred.jaq...@gmail.com wrote:
Looks like somethings messed up in the NAND detection in
the first
place. I am using Redboot FIS to burn the
u-boot-nand.bin . I
know it ignores bad blocks but i had used successfully to
burn in the
Hi Magnus,
Thanks.
If it comes that far it looks like a lot is working. Don't know why
the rest isn't though.
At this point, it should be showing up the processor info. I am using
a custom board with a different flash part. Samsung(KR series), and i
guess it is part of nand_id table as i have
At this point, it should be showing up the processor info. I am using
a custom board with a different flash part. Samsung(KR series), and i
guess it is part of nand_id table as i have used that to get my other
version (patches form internal fresclae git) up and running. But i
believe the
Hi Magnus,
The mainline u-boot + my patches from early April does not contain any
driver for the i.MX31 NAND flash controller so that can't autodetect
any flash part at all.
How does it boot out of NAND then? I am getting confused. By
detection, i meant the basic init of the NFC and the
?
No idea.
Your printk dump from the first mail seems to indicate that the kernel
was able to boot, but for some reason it doesn't print on the serial
port. And I can't see any init of the serial port in that log either.
Seems like a problem with your kernel or its configuration.
/Magnus
Hi Magnus,
Thanks!
Here's a 'snapshot' function in git-web
(http://git.denx.de/?p=u-boot.git;a=tree) which will produce a tarball
of the current tree.
Before that, i actually managed to git clone to a windows machine(at
my home) and export the u-boot tarball to my office linux host where
its
Hi
2009/4/28 alfred steele alfred.jaq...@gmail.com:
Hi Magnus,
Thanks!
But then on doing make mx31_pdk_config, i got the following:
$ make mx31ads_config
: invalid option
make: *** [mx31ads_config] Error 1
So looks like somewhere out there , some file has some weird windows
inherited
Hi Magnus,
No, but it seems that the problem is in the patched Makefile since it
says mx31ads_config instead of mx31_pdk_config.
I tried this on all the RULES as i was getting the same results for
the rule mx31_pdk_config. Apologize for for posting the wrong one.
This problem got resolved when
Hi Magnus,
So , in order to boot out of NAND, all i need to do is use the image
generated out mx31pdk_nand_config instead of the regular
mx31_pdk_config. Right?
Another thing which confuses me is the file nand_boot_mx31.c . Is it
a symbolik link which points to the genric nand_boot.c or is it
So , in order to boot out of NAND, all i need to do is use the image
generated out mx31pdk_nand_config instead of the regular
mx31_pdk_config. Right?
Yes.
/Magnus
___
U-Boot mailing list
U-Boot@lists.denx.de
Hi
2009/4/28 alfred steele alfred.jaq...@gmail.com:
Hi Magnus,
So , in order to boot out of NAND, all i need to do is use the image
generated out mx31pdk_nand_config instead of the regular
mx31_pdk_config. Right?
Another thing which confuses me is the file nand_boot_mx31.c . Is it
a
Hi Magnus,
Thanks again!
The nand_spl/nand_boot_mx31.c is a regular file if that's the one you mean.
The reason i am asking is I am getting a build error related to this
file after i apply your patches. When i do a ll(ls -l) on the file, i
get
$ll
2009/4/28 alfred steele alfred.jaq...@gmail.com:
Hi Magnus,
Thanks again!
The nand_spl/nand_boot_mx31.c is a regular file if that's the one you mean.
The reason i am asking is I am getting a build error related to this
file after i apply your patches. When i do a ll(ls -l) on the file, i
Dear Magnus,
Yes, that's the latest one I've posted (I've done minor updates
locally but haven't tested those yet).
I guess that's there are two patches for NAND_SPL, one which just adds
the SPL framework and the other which creates the mx31pdk_nand.c and
changes to start.S.
Please correct me
Or you suggest sticking to the latest and greatest mainline.
Alternatively, will use the .rej to generate the new lot of patches.
That seems the best route.
Thanks.
___
U-Boot mailing list
U-Boot@lists.denx.de
Hi
2009/4/28 alfred steele alfred.jaq...@gmail.com:
Dear Magnus,
Yes, that's the latest one I've posted (I've done minor updates
locally but haven't tested those yet).
I guess that's there are two patches for NAND_SPL, one which just adds
the SPL framework and the other which creates the
Please correct me if i am wrong. Since the cpu/arm1136/start.S has
changed in a major way since April 02, since this is a generic file, i
am getting a BIG .rej file for the HUNKS which failed. I can hand edit
start.S as i have done for the rest of the HUNK failures which were
minor. But is
Hi Magnus,
I just applied the patch series to the current u-boot tip and the only
problem was the top Makefile but that was easy to fix. No warnings
from start.S.
I was able to build successfully after hand editing some of the hunks
in start.S. Even after using the commit snapshot you had
I think the first step would be to get MX31PDK into mainline U-boot. Are you
willing to help on that?
Of course, as long as i have it up and running and tested on my
hardware. But in order to do that, i would need your help in answering
my earlier question.
Thanks for your help!
-Alfred.
Hi
2009/4/27 alfred steele alfred.jaq...@gmail.com:
I think the first step would be to get MX31PDK into mainline U-boot. Are you
willing to help on that?
Of course, as long as i have it up and running and tested on my
hardware. But in order to do that, i would need your help in answering
my
Dear Magnus,
Thanks for the reply!
And we need to know which U-boot patches you're using to boot the PDK
board.
I am using the internal git tree code supplied to me by freescale. The
tarball is called uboot-imx-imx_v2009.01.tar.gz. I can boot uboot
out of NAND successfully using that as the
the kernel. My
bootup sequence too hangs after Uncompressing kernel...done booting
the kernel.
Thanks.
On Fri, Apr 24, 2009 at 1:23 PM, Fabio Estevam fabioeste...@yahoo.com wrote:
Hi Alfred,
--- On Thu, 4/23/09, alfred steele alfred.jaq...@gmail.com wrote:
I have attached the printk circular
Dear alfred steele,
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
(see http://www.netmeister.org/news/learn2quote.html)
In message
Dear Wolfgang,
You top post.
You full quote.
Sincere Apologies. I better watch out before i hit the send button.
Best Regards.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi All,
I am using mx31 pdk and uImage generated by LTIB.
Basically, my problem is my kernel gets stuck after printing the
Done...Booting the kernel. Please the responses below.
Upon inspecting the printk log by doing a memory dump of the _buf_log
symbol in System.map(i translated
58 matches
Mail list logo
