On Thursday 12 April 2007 11:49 am, Jason Wessel wrote:
> J. Mayer wrote:
> > On Wed, 2007-04-11 at 17:49 -0400, Rob Landley wrote:
> >
> >> qemu-system-ppc -M prep -nographic -kernel zImage-powerpc -append \
> >> "console=/dev/ttyS0"
...
> While I am sure folks have the objective to be able
On Thursday 12 April 2007 11:49 am, Jason Wessel wrote:
> J. Mayer wrote:
> > On Wed, 2007-04-11 at 17:49 -0400, Rob Landley wrote:
> >
> >> qemu-system-ppc -M prep -nographic -kernel zImage-powerpc -append \
> >> "console=/dev/ttyS0"
> >>
> >
> > You cannot append anything to the comman
I'm fighting with cvs and haven't been able to update my build directory yet.
(I've been spoiled by mercurial, where doing an update on a directory with
modifications in it doesn't _eat_ the directory. And my attempt to create a
mercurial copy of the cvs history with tailor so I could tracck d
J. Mayer wrote:
On Thu, 2007-04-12 at 10:49 -0500, Jason Wessel wrote:
A kernel > 4 MB ? Even on my amd64 I usually have kernels smaller than
this. Is there any need to have such a big kernel for anyone ?
Maybe no one else has the need but me... I built a kernel with nearly
all built i
On Thu, 2007-04-12 at 10:49 -0500, Jason Wessel wrote:
> J. Mayer wrote:
> > On Wed, 2007-04-11 at 17:49 -0400, Rob Landley wrote:
> >
> >> qemu-system-ppc -M prep -nographic -kernel zImage-powerpc -append \
> >> "console=/dev/ttyS0"
> >>
> >
> > You cannot append anything to the command
Jason Wessel wrote:
There is a new regression between Apr 9 and Apr 10 in the QEMU CVS
HEAD where tcp checksums are failing again. :-(
I stand corrected it not the TCP check sums. The new PPC pic code does
not work so as to allow the ethernet device driver to receive packets.
I guess t
J. Mayer wrote:
On Wed, 2007-04-11 at 17:49 -0400, Rob Landley wrote:
qemu-system-ppc -M prep -nographic -kernel zImage-powerpc -append \
"console=/dev/ttyS0"
You cannot append anything to the command line this way, with the PPC
firmware...
You can append options when using yaboot, n
On Wed, 2007-04-11 at 17:49 -0400, Rob Landley wrote:
> On Monday 09 April 2007 6:32 pm, J. Mayer wrote:
> > On Mon, 2007-04-09 at 17:26 -0400, Rob Landley wrote:
> > > On Sunday 08 April 2007 7:19 pm, Paul Brook wrote:
> > [...]
> >
> > > > AFAIK PPC emulation hasn't *ever* worked well enough t
On Monday 09 April 2007 6:32 pm, J. Mayer wrote:
> On Mon, 2007-04-09 at 17:26 -0400, Rob Landley wrote:
> > On Sunday 08 April 2007 7:19 pm, Paul Brook wrote:
> [...]
>
> > > AFAIK PPC emulation hasn't *ever* worked well enough to boot without at
> > least
> > > building a custom linux kernel.
On Mon, 2007-04-09 at 17:26 -0400, Rob Landley wrote:
> On Sunday 08 April 2007 7:19 pm, Paul Brook wrote:
[...]
> > AFAIK PPC emulation hasn't *ever* worked well enough to boot without at
> least
> > building a custom linux kernel. In addition the -kernel commandline option
> > have no effect
On Sunday 08 April 2007 7:19 pm, Paul Brook wrote:
> > Mr Paul Brook did break the PREP and heathrow machines while doing
> > changes in the PCI code. There were some posts on this list reporting
> > this and he never even tried to fix what he broke. And now he's
> > complaining "I cannot test as i
On Mon, 2007-04-09 at 00:19 +0100, Paul Brook wrote:
> > Mr Paul Brook did break the PREP and heathrow machines while doing
> > changes in the PCI code. There were some posts on this list reporting
> > this and he never even tried to fix what he broke. And now he's
> > complaining "I cannot test as
On Sunday 08 April 2007, Paul Brook wrote:
> I stand by my original statement.
> A machine that requires building a custom kernel, maybe hacking a
> bootloader, and creating a bootable filesystem from scratch is untestable.
seems reasonable to me
-mike
pgpDRIrvITBvj.pgp
Description: PGP signatur
> Mr Paul Brook did break the PREP and heathrow machines while doing
> changes in the PCI code. There were some posts on this list reporting
> this and he never even tried to fix what he broke. And now he's
> complaining "I cannot test as it does not work". Looks like a bad joke,
> no ?
AFAIK PPC
On Sun, 2007-04-08 at 15:11 +0100, Thiemo Seufer wrote:
> J. Mayer wrote:
> [snip]
> > Mr Paul Brook did break the PREP and heathrow machines while doing
> > changes in the PCI code. There were some posts on this list reporting
> > this and he never even tried to fix what he broke. And now he's
> >
J. Mayer wrote:
[snip]
> Mr Paul Brook did break the PREP and heathrow machines while doing
> changes in the PCI code. There were some posts on this list reporting
> this and he never even tried to fix what he broke. And now he's
> complaining "I cannot test as it does not work". Looks like a bad j
The main problem here is that the less one can do when collaborating to
a project is to respect others work.
Then nobody should ever commit anything that touch the code he's not in
charge without previously formally do a proposal, wait for reactions and
discuss, taking care of others remarks, espec
17 matches
Mail list logo
