3 Aug 2003 14:26
4 Aug 2003 20:32
Re: synthetic serial driver
Andrew Lunn <andrew <at> lunn.ch>
2003-08-04 18:32:28 GMT
2003-08-04 18:32:28 GMT
On Sun, Aug 03, 2003 at 02:26:21PM +0200, Savin Zlobec wrote: > Hello, > > this is a serial driver for ecosynth target wich > can be used to access real serial ports or pseudo > ttys. Great. Hopefully Bart or someone can find some time to take a closer look ready for inclusion into eCos. We will need a copyright assignment for this. Please could you take a look at http://sources.redhat.com/ecos/assign.html. I also noticed in the ChangeLog you say some code was based on that from Philippe Moutarlier. Could you show us which parts? We may also need an assignment from Philippe. Thanks Andrew
5 Aug 2003 00:10
Re: synthetic serial driver
Savin Zlobec <savin <at> torina.fe.uni-lj.si>
2003-08-04 22:10:27 GMT
2003-08-04 22:10:27 GMT
Hi! I've already mailed my assignment a week ago. But I guess that mail needs about two weeks from here to US. The code wich uses a buffer to fetch charachters from auxiliary is based on code send to me from Philippe Moutarlier - but I rewrote and modified it so there is little of original code left. I can post here the diffs of Philippe's changes if it is of any help. savin
5 Aug 2003 09:26
Re: synthetic serial driver
Andrew Lunn <andrew.lunn <at> ascom.ch>
2003-08-05 07:26:53 GMT
2003-08-05 07:26:53 GMT
On Tue, Aug 05, 2003 at 12:10:27AM +0200, Savin Zlobec wrote:
> Hi!
>
> I've already mailed my assignment a week ago. But I guess
> that mail needs about two weeks from here to US.
Thats great. Thanks
>
> The code wich uses a buffer to fetch charachters
> from auxiliary is based on code send to me from
> Philippe Moutarlier - but I rewrote and modified
> it so there is little of original code left.
>
> I can post here the diffs of Philippe's changes if it
> is of any help.
Yes please.
Andrew
5 Aug 2003 15:41
Re: synthetic serial driver
Savin Zlobec <savin <at> torina.fe.uni-lj.si>
2003-08-05 13:41:47 GMT
2003-08-05 13:41:47 GMT
On Tue, 5 Aug 2003, Andrew Lunn wrote: > On Tue, Aug 05, 2003 at 12:10:27AM +0200, Savin Zlobec wrote: > > Hi! > > > > I've already mailed my assignment a week ago. But I guess > > that mail needs about two weeks from here to US. > > Thats great. Thanks > > > > > The code wich uses a buffer to fetch charachters > > from auxiliary is based on code send to me from > > Philippe Moutarlier - but I rewrote and modified > > it so there is little of original code left. > > > > I can post here the diffs of Philippe's changes if it > > is of any help. > > Yes please. > > Andrew > I've attached my old sources and diffs of Philippe's changes. savin
(Continue reading)
5 Aug 2003 20:36
Re: [ECOS] load data from floppy
Savin Zlobec <savin <at> torina.fe.uni-lj.si>
2003-08-05 18:36:29 GMT
2003-08-05 18:36:29 GMT
Gary Thomas <gary <at> mlbassoc.com> writes: > On Wed, 2003-07-30 at 08:23, Nick Garnett wrote: > > Gary Thomas <gary <at> mlbassoc.com> writes: > > > > > On Wed, 2003-07-30 at 04:36, Nick Garnett wrote: > > > > davidw <at> dedasys.com (David N. Welton) writes: > > > > > > > > > Nick Garnett <nickg <at> ecoscentric.com> writes: > > > > > > > > > > > > > I'm having a go at making a floppy driver, but it doesn't appear > > > > > > > to be particularly simple:-/ > > > > > > > > > > > > I seem to recall that the PC floppy hardware is really nasty to > > > > > > program. IDE is a doddle by comparison. > > > > > > > > > > You're right. It's a very unpleasant interface. > > > > > > > > > > I managed to beat the relevant Minix code into shape to do what I > > > > > need. Would this be of any interest to you guys? I'm sure it needs > > > > > an expert hand to really bring it up to snuff, but it does work for > > > > > reading a floppy. The license is the new BSD-style Minix license. > > > > > > > > > > > > > It would certainly be worth looking at. We also need to make sure that > > > > way you are using it matches with the (currently very vague) ideas I > > > > have about how block devices should work. There are also issues of > > > > packaging, configuration and coding style to worry about. > > > > > > > > > > Are any of these ideas written down? I ask, in particular, because(Continue reading)
9 Aug 2003 08:29
cyg_thread_kill vs SMP
Jonathan Larmour <jifl <at> eCosCentric.com>
2003-08-09 06:29:23 GMT
2003-08-09 06:29:23 GMT
Cyg_Thread::kill() contains:
switch( sleep_reason ) {
case NONE:
// The thread is not sleeping for any reason, it must be
// on a run queue.
// We can safely deschedule and set its state.
if( state == RUNNING ) Cyg_Scheduler::scheduler.rem_thread(this);
state = EXITED;
break;
Isn't this wrong for SMP?
Jifl
--
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
11 Aug 2003 12:47
Re: cyg_thread_kill vs SMP
Nick Garnett <nickg <at> ecoscentric.com>
2003-08-11 10:47:00 GMT
2003-08-11 10:47:00 GMT
Jonathan Larmour <jifl <at> eCosCentric.com> writes:
> Cyg_Thread::kill() contains:
> switch( sleep_reason ) {
> case NONE:
> // The thread is not sleeping for any reason, it must be
> // on a run queue.
> // We can safely deschedule and set its state.
> if( state == RUNNING ) Cyg_Scheduler::scheduler.rem_thread(this);
> state = EXITED;
> break;
>
> Isn't this wrong for SMP?
I think it's OK. rem_thread() will detect that the thread is actually
running on a different CPU and send it a reschedule interrupt. By the
time we come to release the scheduler lock, that other CPU should be
spinning waiting to claim it. The only reason it might not be is if it
is running with interrupts disabled, in which case thread state is
irrelevant, and it will fall in to the reschedule interrupt as soon as
they are re-enabled.
--
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
15 Aug 2003 16:27
Host tools configuration
Gary Thomas <gary <at> mlbassoc.com>
2003-08-15 14:27:32 GMT
2003-08-15 14:27:32 GMT
Bart,
I'm having trouble building the ConfigTool. I'm using a Debian
development system (don't ask!) and building of ecosconfig fails
because -ldl isn't being included in the link. I think this is
because your scripts expect ${TCL_LIB_SPEC} to include everything
to link a TCL program, but I think you need to add ${TCL_LIBS}
to it.
What I want to (at least try) is this:
gthomas <at> artemis:/work/tools/BUILD/ecos$ diff -u acsupport/acinclude.m4{~,}
--- acsupport/acinclude.m4~ Wed Feb 12 13:31:52 2003
+++ acsupport/acinclude.m4 Fri Aug 15 08:02:15 2003
<at> <at> -543,7 +543,7 <at> <at>
if test -z "${TCL_LIB_SPEC}" ; then
AC_MSG_ERROR(${tclconfig}/tclConfig.sh does not define TCL_LIB_SPEC, and unable to find libtcl.a)
fi
- ecos_LIBS="${ecos_LIBS} ${TCL_LIB_SPEC}"
+ ecos_LIBS="${ecos_LIBS} ${TCL_LIB_SPEC} ${TCL_LIBS}"
dnl Next, look for tkConfig.sh
possibles=`echo ${possibles} | sed -e 's,tcl,tk,g'`
My problem is though - what's the magic to regenerate all of the
'configure' files once this has changed?
Thanks for your help.
--
--
Gary Thomas <gary <at> mlbassoc.com>
(Continue reading)
17 Aug 2003 21:42
Re: Host tools configuration
Bart Veer <bartv <at> ecoscentric.com>
2003-08-17 19:42:09 GMT
2003-08-17 19:42:09 GMT
>>>>> "Gary" == Gary Thomas <gary <at> mlbassoc.com> writes:
Gary> Bart,
Gary> I'm having trouble building the ConfigTool. I'm using a
Gary> Debian development system (don't ask!) and building of
Gary> ecosconfig fails because -ldl isn't being included in the
Gary> link. I think this is because your scripts expect
Gary> ${TCL_LIB_SPEC} to include everything to link a TCL program,
Gary> but I think you need to add ${TCL_LIBS} to it.
Which particular version of Debian are you using? One of my machines
runs Debian 3.0, which shipped with Tcl 8.3.3, and I have not had any
problems rebuilding ecosconfig.
Gary> What I want to (at least try) is this:
Gary> gthomas <at> artemis:/work/tools/BUILD/ecos$ diff -u acsupport/acinclude.m4{~,}
Gary> --- acsupport/acinclude.m4~ Wed Feb 12 13:31:52 2003
Gary> +++ acsupport/acinclude.m4 Fri Aug 15 08:02:15 2003
Gary> <at> <at> -543,7 +543,7 <at> <at>
Gary> if test -z "${TCL_LIB_SPEC}" ; then
Gary> AC_MSG_ERROR(${tclconfig}/tclConfig.sh does not define TCL_LIB_SPEC, and unable to find libtcl.a)
Gary> fi
Gary> - ecos_LIBS="${ecos_LIBS} ${TCL_LIB_SPEC}"
Gary> + ecos_LIBS="${ecos_LIBS} ${TCL_LIB_SPEC} ${TCL_LIBS}"
Gary> dnl Next, look for tkConfig.sh
Gary> possibles=`echo ${possibles} | sed -e 's,tcl,tk,g'`
Unfortunately every time these libraries change it seems to break on
one platform or another. The current set of libraries seems to have
(Continue reading)
RSS Feed