* boot loader
[not found] <36E192B5.6C18381B@noaa.gov>
@ 1999-03-07 1:04 ` Cort Dougan
1999-03-08 10:14 ` Gabriel Paubert
0 siblings, 1 reply; 10+ messages in thread
From: Cort Dougan @ 1999-03-07 1:04 UTC (permalink / raw)
To: linuxppc-dev
I haven't seen any candidate bootloaders so I'm starting with the current
arch/ppc/boot/
I did some cleanups today and committed them to cvs. I'll put a tar file
up at linuxppc.cs.nmt.edu/pub/linuxppc/kernel-source shortly. Please
take a look at that code and let me know the problems you have with it.
We'll build from there.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: boot loader
1999-03-07 1:04 ` boot loader Cort Dougan
@ 1999-03-08 10:14 ` Gabriel Paubert
1999-03-08 19:33 ` Cort Dougan
0 siblings, 1 reply; 10+ messages in thread
From: Gabriel Paubert @ 1999-03-08 10:14 UTC (permalink / raw)
To: Cort Dougan; +Cc: linuxppc-dev
On Sat, 6 Mar 1999, Cort Dougan wrote:
>
> I haven't seen any candidate bootloaders so I'm starting with the current
> arch/ppc/boot/
Sorry about that. I did not have much time lately.
>
> I did some cleanups today and committed them to cvs. I'll put a tar file
Which cvs ?
Gabriel.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: boot loader
1999-03-08 10:14 ` Gabriel Paubert
@ 1999-03-08 19:33 ` Cort Dougan
0 siblings, 0 replies; 10+ messages in thread
From: Cort Dougan @ 1999-03-08 19:33 UTC (permalink / raw)
To: Gabriel Paubert; +Cc: linuxppc-dev
I understand.
}Sorry about that. I did not have much time lately.
VGER. Until bitkeeper is ready (a couple weeks it looks like) I'll be
putting things on vger and creating tarballs at linuxppc.cs.nmt.edu.
}> I did some cleanups today and committed them to cvs. I'll put a tar file
}
}Which cvs ?
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Boot Loader
@ 2002-12-09 6:05 Erik Christiansen
2002-12-09 7:43 ` Wolfgang Denk
0 siblings, 1 reply; 10+ messages in thread
From: Erik Christiansen @ 2002-12-09 6:05 UTC (permalink / raw)
To: linuxppc-embedded
G'day,
Having proved the gnu powerpc-linux toolchain by building and
running a simple program on our custom ppc850SAR board, the next step
seems to be a boot loader.
Had a look at http://sourceforge.net/projects/u-boot , as recently
mentioned by Jerry Van Baren, but the site states "This Project Has Not
Released Any Files", and the cvs repository link states "Only project
developers can access the CVS tree via this method."
So, instead, I've downloaded ppcboot-2.0.0., which seems to be the
maiden name of u-boot, anyway.
Until the U-Boot surfaces, would this be a good way to go, when faced
with a custom board?
Regards,
Erik
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Boot Loader
2002-12-09 6:05 Erik Christiansen
@ 2002-12-09 7:43 ` Wolfgang Denk
2002-12-10 7:54 ` Erik Christiansen
0 siblings, 1 reply; 10+ messages in thread
From: Wolfgang Denk @ 2002-12-09 7:43 UTC (permalink / raw)
To: Erik Christiansen; +Cc: linuxppc-embedded
In message <20021209060509.GA5743@dd•nec.com.au> you wrote:
>
> Had a look at http://sourceforge.net/projects/u-boot , as recently
> mentioned by Jerry Van Baren, but the site states "This Project Has Not
> Released Any Files", and the cvs repository link states "Only project
> developers can access the CVS tree via this method."
It is correct that we haven't released an official version of U-Boot
yet, but as you can see from the project page it is based on PPCBoot,
which has been around for _some_ time.
And of course the CVS repository _is_ available to everybody for
anonymous CVS access. The page you quote is pretty clear:
Anonymous CVS Access
This project's SourceForge.net CVS repository can be checked
out through anonymous (pserver) CVS with the following
instruction set. The module you wish to check out must be
specified as the modulename. When prompted for a password for
anonymous, simply press the Enter key.
cvs -d:pserver:anonymous@cvs•u-boot.sourceforge.net:/cvsroot/u-boot login
cvs -z3 -d:pserver:anonymous@cvs•u-boot.sourceforge.net:/cvsroot/u-boot co modulename
Updates from within the module's directory do not need the
-d parameter.
Developer access is indeed for developers only.
> Until the U-Boot surfaces, would this be a good way to go, when faced
> with a custom board?
No. You should not spend time on a project which has been
discontinued. Just download the latest (top of tree) version from the
U-Boot CVS server.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx•de
Ernest asks Frank how long he has been working for the company.
"Ever since they threatened to fire me."
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Boot Loader
2002-12-09 7:43 ` Wolfgang Denk
@ 2002-12-10 7:54 ` Erik Christiansen
0 siblings, 0 replies; 10+ messages in thread
From: Erik Christiansen @ 2002-12-10 7:54 UTC (permalink / raw)
To: linuxppc-embedded
On Mon, Dec 09, 2002 at 08:43:47AM +0100, Wolfgang Denk wrote:
>
> No. You should not spend time on a project which has been
> discontinued. Just download the latest (top of tree) version from the
> U-Boot CVS server.
Wolfgang,
Thank you for setting me straight.
Reading the "U-Boot Porting Guide", it looks like time to order in
plenty of pizza.
Regards,
Erik
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Executable delay
[not found] <20031217093448.A18081@lists.linuxppc.org>
@ 2003-12-17 17:11 ` James Bates
2003-12-22 9:58 ` James Bates
0 siblings, 1 reply; 10+ messages in thread
From: James Bates @ 2003-12-17 17:11 UTC (permalink / raw)
To: linuxppc-embedded
Hi All,
I'm getting some funny behaviour on my MPC8260ADS based system.
I am mounting my DiskOnChip 2000 on /mnt/doc. It all seems fine until I try
executing something from it. Trying to execute anything from the doc takes
ages, execution will not occur until a good 2 minutes after you have typed
the command. I have tried this with the most basic of programs and it still
does the same. Everthing runs fine when executed from the nfs mounted root
filesystem.
I know that this is not a hardware problem because I can boot into Bluecat
linux and access the filesystem without problems.
I have tried setting Use short timeouts but it makes no difference.
I have the latest eldk and 2.4.23 kernel from linuxppc_2_4_devel.
Looking into this problem a little deeper we put a logic analyser on the
DiskOnChip and discovered.
1) All large reads ( > ~10K get stuck)
2) Looking at the "top" output. Any process that accesses the DOC quickly
gets put into the D state (Task Uninterruptable).
3) Kicking off a new process brings the accessing process to life for a
short while it then goes back into the task uninterruptable state.
It smells like an mtd driver problem but I havn't the foggiest where to
start looking for the solution. Any ideas greatly received.
Kind Regards,
James Bates
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Executable delay
2003-12-17 17:11 ` Executable delay James Bates
@ 2003-12-22 9:58 ` James Bates
2003-12-22 11:59 ` Boot Loader Kevin A. Sapp
0 siblings, 1 reply; 10+ messages in thread
From: James Bates @ 2003-12-22 9:58 UTC (permalink / raw)
To: linuxppc-embedded
Hi All,
I have had my first real poke around the kernel and it looks like I was
correct in saying that any task accessing the DOC drivers was put into an
incorrect state. The code that seemed to do the damage can be found in
drivers/mtd/devices/doc2000.c in the function _DoC_WaitReady().
The problem seems to be the call to cond_resched which is not in slightly
older kernel versions. To fix the bug I reverted this function back to the
code in version 2.4.10 of the kernel.
After making these changes it appears to work perfectly. My question now is.
Have I inadvertently broken something without knowing it.
Kind Regards,
James Bates
PS: My _DoC_WaitReady is as follows:
/* DOC_WaitReady: Wait for RDY line to be asserted by the flash chip */
static int _DoC_WaitReady(struct DiskOnChip *doc)
{
unsigned long docptr = doc->virtadr;
#ifndef CONFIG_MTD_DOCPROBE_SHORT_TIMEOUTS
unsigned long timeo = jiffies + (HZ * 10);
#else
unsigned long timeo = jiffies + 1;
#endif
DEBUG(MTD_DEBUG_LEVEL3,
"_DoC_WaitReady called for out-of-line wait\n");
/* Out-of-line routine to wait for chip response */
while (!(ReadDOC(docptr, CDSNControl) & CDSN_CTRL_FR_B)) {
if (time_after(jiffies, timeo)) {
DEBUG(MTD_DEBUG_LEVEL2, "_DoC_WaitReady timed out.\n");
return -EIO;
}
// This is the "new" code from version 2.4.23
// udelay(1);
// cond_resched();
// Revert back to old task state management in 2.4.10
if (current->need_resched) {
set_current_state(TASK_UNINTERRUPTIBLE);
schedule_timeout(1);
}
else
udelay(1);
// End of 2.4.10 code
}
return 0;
}
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Boot Loader
2003-12-22 9:58 ` James Bates
@ 2003-12-22 11:59 ` Kevin A. Sapp
2003-12-22 13:08 ` Wolfgang Denk
0 siblings, 1 reply; 10+ messages in thread
From: Kevin A. Sapp @ 2003-12-22 11:59 UTC (permalink / raw)
To: linuxppc-embedded
Hello,
For my end target I have to boot across a shared memory
interface by placing the executable into RAM. This is
part of a multi processor system where the Linux board
is a cPCI slave. The Linux board will not have a flash
or a network connection. I is held in reset by the master
until the s/w is loaded and then released. This is an 8275
target. The "Master" is a Solaris Workstation or a PC
style Linux box or card.
Any suggestions on how to do this ?
Have to fill in my own board info in a bd_t struct,
pass it in R3, if I use and initrd it's start and end ptrs
go into R4, R5 and the cmd line params will
be hard coded and inserted into R6,R7...
I will be using a RAM disk for the root file system.
Instead of compressing and creating uImage for das u-boot,
I create a binary(?) image and just shove it into RAM at
0? Ensure the Reset vec is set to my initialization code
that will be part of the download...
Any ideas would be appreciated.
Thank you
Kevin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Boot Loader
2003-12-22 11:59 ` Boot Loader Kevin A. Sapp
@ 2003-12-22 13:08 ` Wolfgang Denk
0 siblings, 0 replies; 10+ messages in thread
From: Wolfgang Denk @ 2003-12-22 13:08 UTC (permalink / raw)
To: Kevin A. Sapp; +Cc: linuxppc-embedded
Dear Kevin,
in message <3FE6DCB3.109@catapult•com> you wrote:
>
> For my end target I have to boot across a shared memory
> interface by placing the executable into RAM. This is
> part of a multi processor system where the Linux board
> is a cPCI slave. The Linux board will not have a flash
> or a network connection. I is held in reset by the master
> until the s/w is loaded and then released. This is an 8275
This has been done before. See for example the "PN62" configuration
in U-Boot.
> Any suggestions on how to do this ?
Use U-Boot...
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx•de
It all seemed, he thought, to be rather a lot of trouble to go to
just sharpen a razor blade. - Terry Pratchett, _The Light Fantastic_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2003-12-22 13:08 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20031217093448.A18081@lists.linuxppc.org>
2003-12-17 17:11 ` Executable delay James Bates
2003-12-22 9:58 ` James Bates
2003-12-22 11:59 ` Boot Loader Kevin A. Sapp
2003-12-22 13:08 ` Wolfgang Denk
2002-12-09 6:05 Erik Christiansen
2002-12-09 7:43 ` Wolfgang Denk
2002-12-10 7:54 ` Erik Christiansen
[not found] <36E192B5.6C18381B@noaa.gov>
1999-03-07 1:04 ` boot loader Cort Dougan
1999-03-08 10:14 ` Gabriel Paubert
1999-03-08 19:33 ` Cort Dougan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox