On Thursday 11 July 2002 18:43, Jake Burkholder wrote:
> Where exactly in init are you trying to print? If you're in the
> single_user function, you can only use stdio in the forked child
> after it calls setctty. Before that you have to open an fd on
> /dev/console yourself and write(2) to it, o
Apparently, On Thu, Jul 11, 2002 at 09:11:47AM +0400,
Serguei Tzukanov said words to the effect of;
> On Thursday 11 July 2002 02:45, Jake Burkholder wrote:
> >
> > I think this is because your console driver (hc) doesn't have a tty
> > interface, just the low level cn* stuff. If you loo
On Thursday 11 July 2002 02:45, Jake Burkholder wrote:
>
> I think this is because your console driver (hc) doesn't have a tty
> interface, just the low level cn* stuff. If you look at the
> ofw_console driver, it provides a rudimentary tty interface using
> polling and cngetc, cnputc equivalents
On Wednesday 10 July 2002 23:04, Julian Elischer wrote:
> OK so I have to ask.. S/390 as in IBM Mainframem S/390?
Yeas, ESA/390.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Apparently, On Wed, Jul 10, 2002 at 03:54:09PM +0400,
Serguei Tzukanov said words to the effect of;
> Some working notes.
>
> I've written the libc/csu part, kernel successfully starts init and init
> forks off for the execve of -sh,
> (http://tzukanov.narod.ru/freebsd390/bootlog.txt)
>
John Baldwin wrote:
> Why does the cast from 32 to 64 treat r3 as the lower 32-bits when
> a 64-bit return value treats r3 as the upper 32-bits and r2 as the
> lower 32-bits? That is inconsistent and you are going to have
> problems with either one or the other. I also don't understand
> exactly
It sounds like a tty driver problem.
Does the emulator even support this?
Do you have a package, so that people can install your developement
environment and use your patches so they can participate in helping
you code?
-- Terry
Serguei Tzukanov wrote:
>
> Some working notes.
>
> I've writte
OK so I have to ask.. S/390 as in IBM Mainframem S/390?
On Wed, 10 Jul 2002, Serguei Tzukanov wrote:
>
> > td_retval[0] is the low word, and td_retval[1] is the high word, you
> > just need to make sure the values from those two words get returned
> > properly to userland.
>
> 1) syscall ret
On 10-Jul-2002 Serguei Tzukanov wrote:
>
>> td_retval[0] is the low word, and td_retval[1] is the high word, you
>> just need to make sure the values from those two words get returned
>> properly to userland.
>
> 1) syscall returns 32-bit value:
> r2 = rv[0];
> r3 = rv[1];
> r
> td_retval[0] is the low word, and td_retval[1] is the high word, you
> just need to make sure the values from those two words get returned
> properly to userland.
1) syscall returns 32-bit value:
r2 = rv[0];
r3 = rv[1];
r3 is irrelevant here (ABI: "32-bit values returne
On 10-Jul-2002 Serguei Tzukanov wrote:
> Some working notes.
>
> I've written the libc/csu part, kernel successfully starts init and init
> forks off for the execve of -sh,
> (http://tzukanov.narod.ru/freebsd390/bootlog.txt)
> but there is problem with printing from userland, e.g. output from
Some working notes.
I've written the libc/csu part, kernel successfully starts init and init
forks off for the execve of -sh,
(http://tzukanov.narod.ru/freebsd390/bootlog.txt)
but there is problem with printing from userland, e.g. output from
userland are not visible. Write syscall to descs 1,2
12 matches
Mail list logo