Hello, Aurelian,
Thank you for clarification. I've understood the situation.
My comment is not the solution for Rob's problem.
Best Regards,
Shin-ichiro KAWASAKI
(2010/05/11 0:48), Aurelien Jarno wrote:
Shin-ichiro KAWASAKI a écrit :
Hello, Rob,
This mail might be too late, but I want to r
Shin-ichiro KAWASAKI a écrit :
> Hello, Rob,
>
> This mail might be too late, but I want to report you that I
> encountered similar trouble.
>
> Using the linux kernel after the following commit, the qemu-sh
> serial console shows no output.
>
>cd5f107628ab89c5dec5ad923f1c27f4cba41972
>
> T
Hello, Rob,
This mail might be too late, but I want to report you that I
encountered similar trouble.
Using the linux kernel after the following commit, the qemu-sh
serial console shows no output.
cd5f107628ab89c5dec5ad923f1c27f4cba41972
This trouble was discussed in sh-linux ML.
http://m
Rob Landley wrote:
> I found out that "-serial stdio" is apparently trying to open /dev/stdio,
> which Ubuntu 9.04 hasn't got. If I say -serial /dev/tty it works from the
> command line (but not in scripts).
I don't think any Linux systems have /dev/stdio.
/dev/stdin, /dev/stdout, /dev/stderr,
On Sunday 14 March 2010 16:28:32 Aurelien Jarno wrote:
> On Sat, Mar 13, 2010 at 05:11:43PM -0600, Rob Landley wrote:
> > I found out that "-serial stdio" is apparently trying to open /dev/stdio,
> > which Ubuntu 9.04 hasn't got. If I say -serial /dev/tty it works from
> > the command line (but no
On Sat, Mar 13, 2010 at 05:11:43PM -0600, Rob Landley wrote:
> On Saturday 13 March 2010 15:11:03 Rob Landley wrote:
> > On Saturday 13 March 2010 04:26:47 Aurelien Jarno wrote:
> > > On Sat, Mar 13, 2010 at 01:51:35AM -0600, Rob Landley wrote:
> > > > Using qemu-system-sh4, this commit:
> > > >
>
On Saturday 13 March 2010 15:11:03 Rob Landley wrote:
> On Saturday 13 March 2010 04:26:47 Aurelien Jarno wrote:
> > On Sat, Mar 13, 2010 at 01:51:35AM -0600, Rob Landley wrote:
> > > Using qemu-system-sh4, this commit:
> > >
> > > e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 is first bad commit
> > >
On Saturday 13 March 2010 04:26:47 Aurelien Jarno wrote:
> On Sat, Mar 13, 2010 at 01:51:35AM -0600, Rob Landley wrote:
> > Using qemu-system-sh4, this commit:
> >
> > e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 is first bad commit
> > commit e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59
> > Author: Gerd H
On Sat, Mar 13, 2010 at 01:51:35AM -0600, Rob Landley wrote:
> Using qemu-system-sh4, this commit:
>
> e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 is first bad commit
> commit e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59
> Author: Gerd Hoffmann
> Date: Tue Dec 8 13:11:44 2009 +0100
>
> zap serial
2010/3/13 Rob Landley :
> Using qemu-system-sh4, this commit:
>
> e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 is first bad commit
> commit e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59
> Author: Gerd Hoffmann
> Date: Tue Dec 8 13:11:44 2009 +0100
>
>zap serial_monitor_mux
>
>The logic in this co
Using qemu-system-sh4, this commit:
e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 is first bad commit
commit e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59
Author: Gerd Hoffmann
Date: Tue Dec 8 13:11:44 2009 +0100
zap serial_monitor_mux
The logic in this code obviously predates the multiple
11 matches
Mail list logo