[U-Boot-Users] RE: U-Boot-Users digest, Vol 1 #1713 - 14 msgs

Darin Lo darin.lo at msa.hinet.net
Mon Feb 20 02:26:30 CET 2006


Dear sir,

I want to unable my U-Boot-Users account .

Please do not send me email again.

Thank you



-----Original Message-----
From: u-boot-users-admin at lists.sourceforge.net
[mailto:u-boot-users-admin at lists.sourceforge.net] On Behalf Of
u-boot-users-request at lists.sourceforge.net
Sent: Sunday, February 19, 2006 11:07 PM
To: u-boot-users at lists.sourceforge.net
Subject: U-Boot-Users digest, Vol 1 #1713 - 14 msgs

Send U-Boot-Users mailing list submissions to
	u-boot-users at lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/u-boot-users
or, via email, send a message with subject or body 'help' to
	u-boot-users-request at lists.sourceforge.net

You can reach the person managing the list at
	u-boot-users-admin at lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of U-Boot-Users digest..."


Today's Topics:

   1. S3C2410 booting from Nand (kalfalfa)
   2. Re: Memory Banks & Flash Mapping (Josef Angermeier)
   3. Re: PPC8xx chip select configuration at startup (Wolfgang Denk)
   4. Re: PPC8xx chip select configuration at startup (Wolfgang Denk)
   5. Re: Re: Safe firmware updates (Wolfgang Denk)
   6. Re: PPC8xx chip select configuration at startup (Wolfgang Denk)
   7. Re: PPC8xx chip select configuration at startup (Jerry Van Baren)
   8. RE: PPC8xx chip select configuration at startup (Steve Strublic)
   9. RE: MPC8xx chip select configuration at startup (Steve Strublic)
  10. Re: PPC8xx chip select configuration at startup (Vladimir
Gurevich)
  11. Re: PPC8xx chip select configuration at startup (Wolfgang Denk)
  12. Flash Configuration in TQM860L? (=?gb2312?B?x9jT7s6w?=)
  13. Re: Flash Configuration in TQM860L? (Wolfgang Denk)
  14. [PATCH] Add target 'cscope' to Makefile (Horst Kronstorfer)

--__--__--

Message: 1
Date: Fri, 17 Feb 2006 11:56:49 -0800 (PST)
From: kalfalfa <kalfalfa at gmail.com>
Reply-To: kalfalfa <kalfalfa at gmail.com>
To: u-boot-users at lists.sourceforge.net
Subject: [U-Boot-Users] S3C2410 booting from Nand


Hi,

I have a board based around the S3C2410 but with no NOR flash, only NAND
flash. This processor can boot from nand by loading the 1st 4k of nand
into
memory and running it (which would then presumably load more things from
nand into ram to run). I'm wondering how to get uBoot running on such a
system? Does it supposrt this, or do I have to write my own 4K
bootloader to
load the uBoot code into ram and start it from there? (and what would be
the
best way of doing that?)

Thanks
-Patrick
--
View this message in context:
http://www.nabble.com/S3C2410-booting-from-Nand-t1142843.html#a2996155
Sent from the Uboot - Users forum at Nabble.com.



--__--__--

Message: 2
From: Josef Angermeier
<Josef.Angermeier at informatik.stud.uni-erlangen.de>
Date: Fri, 17 Feb 2006 21:27:01 +0100
To: Wolfgang Denk <wd at denx.de>
Cc: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] Memory Banks & Flash Mapping


Hello Wolfgang

> > I see. Which files hold the sourcecode to map the flash away ? - I'd
> > like to understand that one!

> That's the memory controller initialization -  function  cpu_init_f()
> in "cpu/mpc8xx/cpu_init.c"

AAAHH! Thanks, i think i finally understood it!

My flash memory space gets now fully initialized in cpu_init_f. Changed
TEXT_BASE to 0x40f00000 and BR0_PRELIM to 0x40000001. 

So MPC875 starts execution at 0xfff00100, because of ignoring the upper
8 address bits and CS0 default usage after reset, u-boot is executed
anyway. When jumping to 0x40fXXXXX, the CPU is aware of the flash
destination and br0 is updated to 0x40000000 to stop aliasing and keep
execution in flash working...  :-))) big thanks goes to Wolfgang!


> Best regards,

> Wolfgang Denk

byebye
Josef



--__--__--

Message: 3
To: Vladimir Gurevich <vag at paulidav.org>
cc: u-boot-users at lists.sourceforge.net
From: Wolfgang Denk <wd at denx.de>
Subject: Re: [U-Boot-Users] PPC8xx chip select configuration at startup 
Date: Fri, 17 Feb 2006 21:48:22 +0100

In message <43F6091D.7040901 at paulidav.org> you wrote:
>
> So, yes, the first instruction to be executed is located at 0x0
(that's
> how your CPU works), but then the code works using 0x04000000 as a
base
> and that is fine. The CPU does not care.

This is not correct. Depending on your HRCW the first instruction  is
either fetched from physical address 0x0100, or 0xFFF00100.

And by the way: that's MPC8xx (not PPC... which traditionally usually
refers to a IBM / AMCC processor).

> > The desired location for FLASH memory will be at 0x0400_0000. This
is=
=20
> > the address space to which I link U-Boot.
> >
> That's OK. It will simply limit your SDRAM size to 64M.

And my cause other problems as well. Don't do it. Map flash at a high
address.

Best regards,

Wolfgang Denk

--=20
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Change is the essential process of all existence.
	-- Spock, "Let That Be Your Last Battlefield",
	   stardate 5730.2


--__--__--

Message: 4
To: "Steve Strublic" <SStrublic at hypercom.com>
cc: "Vladimir Gurevich" <vag at paulidav.org>,
    u-boot-users at lists.sourceforge.net
From: Wolfgang Denk <wd at denx.de>
Subject: Re: [U-Boot-Users] PPC8xx chip select configuration at startup 
Date: Fri, 17 Feb 2006 21:52:23 +0100

In message
<482F3C06ECF00C44AEC226520C6FCB1A51ECFF at EXCHANGEVS.HYPERCOM.CO=
M> you wrote:
>=20
> And I agree that the hard reset word may be other than what U-Boot's
> startup sequence requires, but I'm stuck.  I cannot spin the board to
> alter its contents. =20

U-Boot does not have any specific  requirements.  Your  configuration
may  be  sub-optimal, but this just effects where the U-Boot ode ends
up in your flash device; worst  case  is  that  it  leaves  you  with
700...800 kB of unused / unusable space.

> So I need a way to work with what I've got.  If I can do it without
> modifying U-Boot, that's great... but if I can't, then I need a way
tha=
t

No need to modify U-Boot. Just configure it correctly.

Best regards,

Wolfgang Denk

--=20
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"...all the  good  computer  designs  are  bootlegged;  the  formally
planned  products,  if  they  are built at all, are dogs!" - David E.
Lundstrom, "A Few Good Men From Univac", MIT Press, 1987


--__--__--

Message: 5
To: do <dosilasolfamiredo at o2.pl>
cc: u-boot-users at lists.sourceforge.net
From: Wolfgang Denk <wd at denx.de>
Subject: Re: [U-Boot-Users] Re: Safe firmware updates 
Date: Fri, 17 Feb 2006 22:03:23 +0100

In message <dt527p$arr$1 at sea.gmane.org> you wrote:
>
> Yes of course, my mistake - sorry. But by the way, is there a=20
> possibility for safely update u-boot?

Yes, if you have hardware to support this (i. e. two flash banks that
can be swapped, where the "switch" can  be  controlled  by  software,
remembers  it's state when powered off *and* has some kid of watchdog
function to toggle back to the other position in case the system does
not come up). Not many systems support this ;-)

Best regards,

Wolfgang Denk

--=20
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If I don't document something, it's usually either for a good reason,
or a bad reason.  In this case it's a good reason.  :-)
                 - Larry Wall in <1992Jan17.005405.16806 at netlabs.com>


--__--__--

Message: 6
To: "Steve Strublic" <SStrublic at hypercom.com>
cc: "Vladimir Gurevich" <vag at paulidav.org>,
    u-boot-users at lists.sourceforge.net
From: Wolfgang Denk <wd at denx.de>
Subject: Re: [U-Boot-Users] PPC8xx chip select configuration at startup 
Date: Fri, 17 Feb 2006 22:08:03 +0100

In message
<482F3C06ECF00C44AEC226520C6FCB1A51ED01 at EXCHANGEVS.HYPERCOM.CO=
M> you wrote:
>=20
> So guess what.  I got U-boot to run without the 'boot value'
> modification to CS0 I had discussed.  I think my problem was related
to
> my debugging tool, the visionCLICK ICE... I had it configured to set

WHile I have nothing against a  little  Vision*-bashing,  you  should
stay honest here: The tool is probably not to blame...

> values into the target at reset.  So of course the values of BR0/OR0

... this was a pilot error.

> were overridden with whatever I had in there... which were not the
same
> as what the board booted up with.  I hadn't occurred to me to look for
> and turn off this option until you asked for the values.

I always recommend to use a *minimal* init file in your  debug  tool,
just  doing  what  is  unavoidable  (i. e. disable the watchdog). You
should never mess  with  the  memory  controller  configuration  when
trying to debug U-Boot.

Best regards,

Wolfgang Denk

--=20
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Mr. Cole's Axiom:
        The sum of the intelligence on the planet is a constant;
        the population is growing.


--__--__--

Message: 7
Date: Fri, 17 Feb 2006 16:14:28 -0500
From: Jerry Van Baren <gerald.vanbaren at smiths-aerospace.com>
To:  u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] PPC8xx chip select configuration at startup

Wolfgang Denk wrote:
> In message <43F6091D.7040901 at paulidav.org> you wrote:

[snip]

>>> The desired location for FLASH memory will be at 0x0400_0000. This
is 
>>> the address space to which I link U-Boot.
>>>
>> That's OK. It will simply limit your SDRAM size to 64M.
> 
> And my cause other problems as well. Don't do it. Map flash at a high
> address.

Just to be explicit: you _must_ map your flash _well_above_ 0xC000_0000 
(the start of the linux kernel area) if you want to run linux.

Since _you_ control BR0 (don't listen to them hardware engineers), you 
can put it anywhere you want.  0xFF00_0000 is a good spot.  0xFFF0_0000 
is not as good of a spot because it limits you to 16MB of flash.  Think 
big. ;-)

> Best regards,
> 
> Wolfgang Denk

Best regards,
gvb


--__--__--

Message: 8
Subject: RE: [U-Boot-Users] PPC8xx chip select configuration at startup 
Date: Fri, 17 Feb 2006 14:16:57 -0700
From: "Steve Strublic" <SStrublic at hypercom.com>
To: <wd at denx.de>
Cc: "Vladimir Gurevich" <vag at paulidav.org>,
        <u-boot-users at lists.sourceforge.net>

> -----Original Message-----
> From: wd at denx.de [mailto:wd at denx.de]
> Sent: Friday, February 17, 2006 2:08 PM
> To: Steve Strublic
> Cc: Vladimir Gurevich; u-boot-users at lists.sourceforge.net
> Subject: Re: [U-Boot-Users] PPC8xx chip select configuration at
startup
>=20
> In message
> <482F3C06ECF00C44AEC226520C6FCB1A51ED01 at EXCHANGEVS.HYPERCOM.COM> you
> wrote:
> >
> > So guess what.  I got U-boot to run without the 'boot value'
> > modification to CS0 I had discussed.  I think my problem was related
to
> > my debugging tool, the visionCLICK ICE... I had it configured to set
>=20
> WHile I have nothing against a  little  Vision*-bashing,  you  should
> stay honest here: The tool is probably not to blame...
>=20
> > values into the target at reset.  So of course the values of BR0/OR0
>=20
> ... this was a pilot error.

Yup, sure was.

I'm just glad everything is running smoothly.

>=20
> > were overridden with whatever I had in there... which were not the
same
> > as what the board booted up with.  I hadn't occurred to me to look
for
> > and turn off this option until you asked for the values.
>=20
> I always recommend to use a *minimal* init file in your  debug  tool,
> just  doing  what  is  unavoidable  (i. e. disable the watchdog). You
> should never mess  with  the  memory  controller  configuration  when
> trying to debug U-Boot.
>=20
> Best regards,
>=20
> Wolfgang Denk
>=20
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> Mr. Cole's Axiom:
>         The sum of the intelligence on the planet is a constant;
>         the population is growing.




--__--__--

Message: 9
Subject: RE: [U-Boot-Users] MPC8xx chip select configuration at startup
Date: Fri, 17 Feb 2006 14:42:50 -0700
From: "Steve Strublic" <SStrublic at hypercom.com>
To: "Jerry Van Baren" <gerald.vanbaren at smiths-aerospace.com>,
        <u-boot-users at lists.sourceforge.net>

> Wolfgang Denk wrote:
> > In message <43F6091D.7040901 at paulidav.org> you wrote:
>=20
> [snip]
>=20
> >>> The desired location for FLASH memory will be at 0x0400_0000. This
is
> >>> the address space to which I link U-Boot.
> >>>
> >> That's OK. It will simply limit your SDRAM size to 64M.
> >
> > And my cause other problems as well. Don't do it. Map flash at a
high
> > address.
>=20
> Just to be explicit: you _must_ map your flash _well_above_
0xC000_0000
> (the start of the linux kernel area) if you want to run linux.

I didn't know that about Linux... but who says I'm going to run Linux?
(OK, I am, just kidding.)

>=20
> Since _you_ control BR0 (don't listen to them hardware engineers), you
> can put it anywhere you want.  0xFF00_0000 is a good spot.
0xFFF0_0000
> is not as good of a spot because it limits you to 16MB of flash.
Think
> big. ;-)

0xFF00_0000 makes sense to me, and works fine.  It fits in with what
I've seen in other implementations.  As I stated previously, 0x0400_0000
was a purely historical number.  I'll take the recommendations of those
who have been there before... thanks.

>=20
> > Best regards,
> >
> > Wolfgang Denk
>=20
> Best regards,
> gvb

Thanks Jerry,

Steve



--__--__--

Message: 10
Date: Fri, 17 Feb 2006 14:11:20 -0800
From: Vladimir Gurevich <vag at paulidav.org>
To: Wolfgang Denk <wd at denx.de>
CC: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] PPC8xx chip select configuration at startup

Hi Wolfgang,

Wolfgang Denk wrote:
> This is not correct. Depending on your HRCW the first instruction  is
> either fetched from physical address 0x0100, or 0xFFF00100.
>   
My bad, wrt 0x0100 (I was more concerned about aliasing while writing 
the previous email), but my understanding is that typically MPC8xx ports

of U-boot assume that HCRW is configured for the low boot option, don't 
they?
> And by the way: that's MPC8xx (not PPC... which traditionally usually
> refers to a IBM / AMCC processor).
>   
Agreed.
> And my cause other problems as well. Don't do it. Map flash at a high
> address.
>   
What are the other problems? I believe the TQM8xx ports do (or, at least

used to) use this address.

Thanks,
Vladimir



--__--__--

Message: 11
To: Vladimir Gurevich <vag at paulidav.org>
cc: u-boot-users at lists.sourceforge.net
From: Wolfgang Denk <wd at denx.de>
Subject: Re: [U-Boot-Users] PPC8xx chip select configuration at startup 
Date: Fri, 17 Feb 2006 23:30:05 +0100

In message <43F64A08.7020806 at paulidav.org> you wrote:
>=20
> My bad, wrt 0x0100 (I was more concerned about aliasing while
writing=20
> the previous email), but my understanding is that typically MPC8xx
port=
s=20
> of U-boot assume that HCRW is configured for the low boot option,
don't=
=20
> they?

You can chose any setting you  like.  It's  just  that  low  boot  is
usually  the most efficient and flexible one, as it allows to put the
U-Boot code at the begin of the flash memory with room to grow  after
it, so you don't have any nasty gaps and it's trivial to change flash
device sizes.

> What are the other problems? I believe the TQM8xx ports do (or, at
leas=
t=20
> used to) use this address.

See previous postings. And no, TQM uses 0x4000.0000, not 0x0400.0000.

Best regards,

Wolfgang Denk

--=20
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Above all else -- sky.


--__--__--

Message: 12
Date: Sun, 19 Feb 2006 11:45:03 +0800
From: "=?gb2312?B?x9jT7s6w?=" <yuwei_qin at photontec.com>
To: "u-boot-users" <u-boot-users at lists.sourceforge.net>
Subject: [U-Boot-Users] Flash Configuration in TQM860L?

RGVhciBhbGw6DQogICANCiAgICAgSSB3YW50IHRvIGtub3cgdGhlIEZsYXNoIGNvbmZpZ3Vy
YXRp
b24gaW4gVFFNODYwTC5oLg0KICAgIA0KICAgICBQbGVhc2UgaGVscCBtZSBwb2ludCBvdXQg
dGhl
IGJ1Z3MgaW4gdGhlIGZvbGxvd2luZyBjb25maWd1cmF0aW9uOg0KICAgIA0KICAgICAgICAg
VHdv
IEFNMjlMVjE2MCBjaGlwczsNCiAgICAgICAgIEEyOS1BMTAgKE1QQzg2MCkgaXMgY29ubmVj
dGVk
IHRvIEEwLUExOSAoQU0yOUxWMTYwKTsNCiAgICAgICAgIENTMCMgKCBNUEM4NjApIGlzIGNv
bm5l
Y3RlZCB0byBDRSMgKEFNMjlMVjE2MCk7DQogICAgICAgICBPRSMvR1BMX0FCMShNUEM4NjAp
IGlz
IGNvbm5lY3RlZCB0byBPRSMgKEFNMjlMVjE2MCk7DQogICAgICAgICBXRTAjL0JTX0IwIyAo
TVBD
ODYwKSBpcyBjb25uZWN0ZWQgdG8gV0UjKEFNMjlMVjE2MC1jaGlwMSk7DQogICAgICAgICBX
RTIj
L0JTX0IyIyAoTVBDODYwKSBpcyBjb25uZWN0ZWQgdG8gV0UjKEFNMjlMVjE2MC1jaGlwMik7
DQog
ICAgICAgICBCWVRFIyhBTTI5TFYxNjApIGlzIHNldCB0byBWY2M7DQogICAgICAgICBSWS9C
WSMo
QU0yOUxWMTYwKSBpcyBOQz8/Ow0KICAgICAgDQogICAgVGhhbmsgeW91IHZlcnkgbXVjaCEN
Cg0K
ICAgIFlvdXJzIFNpbmNlcmVseSwNCiAgICAgICAgICAgICAgIFl1d2VpIFFpbiAgDQoJICAg
ICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICChoaGhoaGhoaGhoaGhoQ0KoaGh
oaGh
oaGhoaGhoaGhoXl1d2VpX3FpbkBwaG90b250ZWMuY29tDQqhoaGhoaGhoaGhoaGhoaGhoaGh
oTIw
MDYtMDItMTkNCg==



--__--__--

Message: 13
To: "=?gb2312?B?x9jT7s6w?=" <yuwei_qin at photontec.com>
cc: "u-boot-users" <u-boot-users at lists.sourceforge.net>
From: Wolfgang Denk <wd at denx.de>
Subject: Re: [U-Boot-Users] Flash Configuration in TQM860L? 
Date: Sun, 19 Feb 2006 15:44:46 +0100

In message <OF2D8C2186.EFD8D714-ON4825711A.0016169F at photontec.com> you
wr=
ote:
>
RGVhciBhbGw6DQogICANCiAgICAgSSB3YW50IHRvIGtub3cgdGhlIEZsYXNoIGNvbmZpZ3V=
yYXRp
>
b24gaW4gVFFNODYwTC5oLg0KICAgIA0KICAgICBQbGVhc2UgaGVscCBtZSBwb2ludCBvdXQ=
gdGhl
>
IGJ1Z3MgaW4gdGhlIGZvbGxvd2luZyBjb25maWd1cmF0aW9uOg0KICAgIA0KICAgICAgICA=
gVHdv
>
IEFNMjlMVjE2MCBjaGlwczsNCiAgICAgICAgIEEyOS1BMTAgKE1QQzg2MCkgaXMgY29ubmV=
jdGVk
>
IHRvIEEwLUExOSAoQU0yOUxWMTYwKTsNCiAgICAgICAgIENTMCMgKCBNUEM4NjApIGlzIGN=
vbm5l
>
Y3RlZCB0byBDRSMgKEFNMjlMVjE2MCk7DQogICAgICAgICBPRSMvR1BMX0FCMShNUEM4NjA=
pIGlz
>
IGNvbm5lY3RlZCB0byBPRSMgKEFNMjlMVjE2MCk7DQogICAgICAgICBXRTAjL0JTX0IwIyA=
oTVBD
>
ODYwKSBpcyBjb25uZWN0ZWQgdG8gV0UjKEFNMjlMVjE2MC1jaGlwMSk7DQogICAgICAgICB=
XRTIj
>
L0JTX0IyIyAoTVBDODYwKSBpcyBjb25uZWN0ZWQgdG8gV0UjKEFNMjlMVjE2MC1jaGlwMik=
7DQog
>
ICAgICAgICBCWVRFIyhBTTI5TFYxNjApIGlzIHNldCB0byBWY2M7DQogICAgICAgICBSWS9=
CWSMo
>
QU0yOUxWMTYwKSBpcyBOQz8/Ow0KICAgICAgDQogICAgVGhhbmsgeW91IHZlcnkgbXVjaCE=
NCg0K
>
ICAgIFlvdXJzIFNpbmNlcmVseSwNCiAgICAgICAgICAgICAgIFl1d2VpIFFpbiAgDQoJICA=
gICAg
>
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICChoaGhoaGhoaGhoaGhoQ0KoaG=
hoaGh
>
oaGhoaGhoaGhoXl1d2VpX3FpbkBwaG90b250ZWMuY29tDQqhoaGhoaGhoaGhoaGhoaGhoaG=
hoTIw
> MDYtMDItMTkNCg=3D=3D


Please do not send base 64 encoded messages.

Please do not send HTML messages.

Please send plain text only.

Message unreadable, ignored. Sorry.


--__--__--

Message: 14
Date: Sun, 19 Feb 2006 16:06:41 +0100
From: Horst Kronstorfer <crimm at elemaa.net>
To: u-boot-users at lists.sourceforge.net
Subject: [U-Boot-Users] [PATCH] Add target 'cscope' to Makefile

hi!

the following patch adds target 'cscope' to the main makefile. it also
puts the list of directories with source files and the arguments to
`find'
into make variables.


Signed-off-by: Horst Kronstorfer <hkronsto at frequentis.com>

diff --git a/Makefile b/Makefile
index 9305cab..80e3677 100644
--- a/Makefile
+++ b/Makefile
@@ -135,6 +135,14 @@ SUBDIRS	= tools \
 	  post/cpu
 .PHONY : $(SUBDIRS)
 
+# Directories with files for tag generation
+TAGDIRS := $(SUBDIRS) include lib_generic board/$(BOARDDIR) cpu/$(CPU)\
+ lib_$(ARCH) fs/cramfs fs/fat fs/fdos fs/jffs2 net disk rtc dtt
drivers\
+ drivers/sk98lin common
+
+# Arguments to `find' when generating a list of files for tag
generation
+TAGFINDARGS := \( -name CVS -prune \) -o \( -name '*.[ch]' -print \)
+
 
########################################################################
#
 
########################################################################
#
 
@@ -179,19 +187,14 @@ gdbtools:
 depend dep:
 		@for dir in $(SUBDIRS) ; do $(MAKE) -C $$dir .depend ;
done
 
+cscope:
+		find $(TAGDIRS) $(TAGFINDARGS) >cscope.files; cscope -b
-q -k
+
 tags:
-		ctags -w `find $(SUBDIRS) include \
-				lib_generic board/$(BOARDDIR) cpu/$(CPU)
lib_$(ARCH) \
-				fs/cramfs fs/fat fs/fdos fs/jffs2 \
-				net disk rtc dtt drivers drivers/sk98lin
common \
-			\( -name CVS -prune \) -o \( -name '*.[ch]'
-print \)`
+		ctags -w `find $(TAGDIRS) $(TAGFINDARGS)`
 
 etags:
-		etags -a `find $(SUBDIRS) include \
-				lib_generic board/$(BOARDDIR) cpu/$(CPU)
lib_$(ARCH) \
-				fs/cramfs fs/fat fs/fdos fs/jffs2 \
-				net disk rtc dtt drivers drivers/sk98lin
common \
-			\( -name CVS -prune \) -o \( -name '*.[ch]'
-print \)`
+		etags -a `find $(TAGDIRS) $(TAGFINDARGS)`
 
 System.map:	u-boot
 		@$(NM) $< | \
@@ -1838,7 +1841,7 @@ clobber:	clean
 		-o -name '*.srec' -o -name '*.bin' -o -name u-boot.img
\) \
 		-print0 \
 		| xargs -0 rm -f
-	rm -f $(OBJS) *.bak tags TAGS
+	rm -f $(OBJS) *.bak tags TAGS cscope.*
 	rm -fr *.*~
 	rm -f u-boot u-boot.map u-boot.hex $(ALL)
 	rm -f tools/crc32.c tools/environment.c tools/env/crc32.c


-h



--__--__--

_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users


End of U-Boot-Users Digest

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date:
2006/2/17
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date:
2006/2/17
 





More information about the U-Boot mailing list