syllable-kernel — The list is for discussion of Kernel issues by developers

Re: [Syllable-kernel] patch to fix crash when kernel compiled with -O2 or less

[Kristian V. D. V. <va...@li...>]

On Saturday 09 October 2004 5:12 am, Jake Hamby wrote:
> One more patch for today.  I tried building the kernel with "-O2"
> instead of "-O3" and got an illegal instruction crash at the beginning
> of the init process (before it prints anything).  I looked at the
> difference in assembly output in kernel/init.c and noticed that the
> Fork() function is inlined under -O3.  Since Fork() doesn't seem to be
> used anywhere outside of init.c, I changed it to a static inline
> function and commented out the prototype in include/atheos/kernel.h.
> This fixed the problem, and makes things cleaner since the function
> consists of only a single line of inline asm.

Applied.

> BTW, I would suggest using CFLAGS of "-O2 -mpreferred-stack-boundary=2",
> as Linux and FreeBSD do, instead of "-O3" when building the kernel
> because smaller code size is generally more important than the
> additional inlining.  Using the "size" command on kernel.so, I get a
> text size (data and bss sizes are the same) of:
>
> 378602 bytes for -O3
> 363546 bytes for -O2 -mpreferred-stack-boundary=2
>
> for a savings of 15K or about 4%.  Anyway, here's the patch.

Not a bad idea, so that's been done too.  Thanks Jack :)

-- 
Vanders
http://syllable.sourceforge.net/
http://www.liqwyd.com

Re: [Syllable-kernel] patches to include/atheos/string.h macros and kernel/lib/vsprintf.c

[Kristian V. D. V. <va...@li...>]

On Saturday 09 October 2004 12:56 am, Jake Hamby wrote:
> The first set is an upgrade of the assembly macros in
> include/atheos/string.h to the versions in Linux 2.6.8.  Quick summary
> of the changes I merged:

Applied.

> The second patch is to kernel/lib/vsprintf.c and fixes a GCC warning
> that va_arg functions can't pass floats (they are promoted to double) or
> short int (promoted to int).  I fixed the "%hd" code based on the Linux
> version and commented out the "%f" handling altogether as the kernel
> really should be avoiding floating point usage.  I couldn't find any
> instance of "%f" being used anywhere, and the exact same effect can be
> achieved by casting to int and using %d.  Neither Linux 2.4.26 nor Linux
> 2.6.8 support "%f" in vsprintf.

Applied.  Thanks Jack.

-- 
Vanders
http://syllable.sourceforge.net/
http://www.liqwyd.com

Re: [Syllable-kernel] kernel patches for -Wstrict-prototypes

[Kristian V. D. V. <va...@li...>]

On Saturday 09 October 2004 12:17 am, Jake Hamby wrote:
> I'm new to Syllable development but have experience with FreeBSD, Linux,
> and BeOS kernel hacking, so I'm getting up to speed fairly quickly.  The
> code is easy to understand and has been quite fun to hack on so far. 

Hi Jack.  Its nice to see someone interested in the kernel, I hope you'll find 
plenty to interest you.

> Here's a patch with some minor fixes I've found so far.  First, I added
> "-Wstrict-prototypes" to the CFLAGS in kernel/Makefile (copied from the
> Linux kernel CFLAGS) and corrected some warnings where functions were
> declared as "foo()" instead of "foo(void)" as is correct for ANSI C.

Applied.  Thanks.

-- 
Vanders
http://syllable.sourceforge.net/
http://www.liqwyd.com

Re: [Syllable-kernel] kernel patches

[Maritimus <rea...@ih...>]

William Hoggarth wrote:

> On Saturday 09 Oct 2004 00:17, Jake Hamby wrote:
> > Hi all,
> >
> > I'm new to Syllable development but have experience with FreeBSD, Linux,
> > and BeOS kernel hacking, so I'm getting up to speed fairly quickly.  The
> > code is easy to understand and has been quite fun to hack on so far.
>
> Welcome aboard Jake!
>
> Although Syllable has a growing number of developers we don't really have any
> true kernel hackers. So if you decide to hang around you'd be a welcome
> addition to the team. If you want something to get your teeth stuck into the
> scheduler needs improving. Currently, low priority processes/threads can
> suffer from starvation.
>
> Thanks for the patches and I hope you're enjoying Syllable,
>
> Will H

Yeah, and I think Kurt said the scheduler "sucks" :)

    in addition:
Simultaneous multiprocessing causes the system to lock up whenever the Syllable
kernel is compiled with GCC 3.x instead of 2.9x.
The kernel has some lines of i586 instructions hardcoded in assembler (Kurt owned
a Pentium), which prevents booting on older processors. Some kind of accomodation
for i486 level CPUs (486s and lame Pentium clones) would be useful as many of us
have older systems that'd make good test machines. I'd guess it'd only take a few
lines of code, but somebody needs to know how to do it. Would having the kernel
simply not utilise those instructions when an older CPU is ID'ed be practical?
And the system can't be used on most motherboards with SIS chipsets, as PS/2 dies
(null by keyboard and mouse).

Re: [Syllable-kernel] kernel patches

[William H. <me...@wh...>]

On Saturday 09 Oct 2004 00:17, Jake Hamby wrote:
> Hi all,
>
> I'm new to Syllable development but have experience with FreeBSD, Linux,
> and BeOS kernel hacking, so I'm getting up to speed fairly quickly.  The
> code is easy to understand and has been quite fun to hack on so far.

Welcome aboard Jake!

Although Syllable has a growing number of developers we don't really have any 
true kernel hackers. So if you decide to hang around you'd be a welcome 
addition to the team. If you want something to get your teeth stuck into the 
scheduler needs improving. Currently, low priority processes/threads can 
suffer from starvation.

Thanks for the patches and I hope you're enjoying Syllable,

Will H

[Syllable-kernel] patch to fix crash when kernel compiled with -O2 or less

[Jake H. <jh...@an...>]

One more patch for today.  I tried building the kernel with "-O2" 
instead of "-O3" and got an illegal instruction crash at the beginning 
of the init process (before it prints anything).  I looked at the 
difference in assembly output in kernel/init.c and noticed that the 
Fork() function is inlined under -O3.  Since Fork() doesn't seem to be 
used anywhere outside of init.c, I changed it to a static inline 
function and commented out the prototype in include/atheos/kernel.h. 
This fixed the problem, and makes things cleaner since the function 
consists of only a single line of inline asm.

BTW, I would suggest using CFLAGS of "-O2 -mpreferred-stack-boundary=2", 
as Linux and FreeBSD do, instead of "-O3" when building the kernel 
because smaller code size is generally more important than the 
additional inlining.  Using the "size" command on kernel.so, I get a 
text size (data and bss sizes are the same) of:

378602 bytes for -O3
363546 bytes for -O2 -mpreferred-stack-boundary=2

for a savings of 15K or about 4%.  Anyway, here's the patch.

--
Jake Hamby

[Syllable-kernel] patches to include/atheos/string.h macros and kernel/lib/vsprintf.c

[Jake H. <jh...@an...>]

Two more patches to some utility functions which were originally copied 
from the Linux kernel.  I've only been able to do limited testing, but 
everything seems to work okay.

The first set is an upgrade of the assembly macros in 
include/atheos/string.h to the versions in Linux 2.6.8.  Quick summary 
of the changes I merged:

* Removed "cld" instructions from most macros.  They shouldn't be 
necessary as every occurrence of "std" is immediately followed by "cld".

* Changed function macros from "extern inline" to "static inline". 
Shouldn't make any difference.

* Removed the alternate versions of strcat() and strncat().  Changed a 
value from "0xffffffff" to "0xffffffffu" which perhaps was causing a bug 
in the original versions (maybe a GCC 3.x issue?).  I have no idea why 
the original versions were commented out in AtheOS, so that's just my 
guess, as the Syllable CVS server doesn't say.

* memmove() now calls memcpy() if possible (changed in Linux 2.6.x).

* Added an assembly version of strstr(), not inline but in 
kernel/lib/strstr.c (and added to Makefile).

The second patch is to kernel/lib/vsprintf.c and fixes a GCC warning 
that va_arg functions can't pass floats (they are promoted to double) or 
short int (promoted to int).  I fixed the "%hd" code based on the Linux 
version and commented out the "%f" handling altogether as the kernel 
really should be avoiding floating point usage.  I couldn't find any 
instance of "%f" being used anywhere, and the exact same effect can be 
achieved by casting to int and using %d.  Neither Linux 2.4.26 nor Linux 
2.6.8 support "%f" in vsprintf.

--
Jake Hamby

[Syllable-kernel] kernel patches for -Wstrict-prototypes

[Jake H. <jh...@an...>]

Hi all,

I'm new to Syllable development but have experience with FreeBSD, Linux, 
and BeOS kernel hacking, so I'm getting up to speed fairly quickly.  The 
code is easy to understand and has been quite fun to hack on so far.  As 
I'm using VMWare (4.5.2) to host Syllable, my first task is to figure 
out why I can only get it to work reliably with the kernel flag 
"enable_ata_dma=false", which makes things run much slower.

Here's a patch with some minor fixes I've found so far.  First, I added 
"-Wstrict-prototypes" to the CFLAGS in kernel/Makefile (copied from the 
Linux kernel CFLAGS) and corrected some warnings where functions were 
declared as "foo()" instead of "foo(void)" as is correct for ANSI C.

Also in this patchset, I commented out some local functions which were 
not being used, removing the remaining GCC warnings, fixed a typo 
("deamon" -> "daemon") in kernel/swap.c, and fixed panic() in 
kernel/kernel.c to use the va_list macros instead of pointer arithmetic. 
  So these are all basically minor stylistic fixes.

--
Jake Hamby

Re: [Syllable-kernel] trident driver multiple miers patch

[Kristian V. D. V. <va...@li...>]

On Wednesday 06 October 2004 4:10 pm, Colin Phipps wrote:
> I did this little patch to fix an error during startup for my on-board
> sis7018 sound chip. It has two mixers (the second is for the built in
> modem I think - awful hardware), but trident.c was trying to give them
> the same device node. Sound worked without this, but it looks neater in
> the startup with.

Thank you.  Applied.

-- 
Vanders
http://syllable.sourceforge.net/
http://www.liqwyd.com

[Syllable-kernel] trident driver multiple miers patch

[Colin P. <cp...@cp...>]

I did this little patch to fix an error during startup for my on-board
sis7018 sound chip. It has two mixers (the second is for the built in
modem I think - awful hardware), but trident.c was trying to give them
the same device node. Sound worked without this, but it looks neater in
the startup with.

Index: trident.c
===================================================================
RCS file: /cvsroot/syllable/syllable/system/sys/kernel/drivers/sound/trident/trident.c,v
retrieving revision 1.3
diff -p -u -r1.3 trident.c
--- trident.c	18 Nov 2003 13:17:29 -0000	1.3
+++ trident.c	6 Oct 2004 14:25:57 -0000
@@ -2043,6 +2043,7 @@ static int trident_ac97_init(struct trid
 	}
 
 	for (num_ac97 = 0; num_ac97 < NR_AC97; num_ac97++) {
+		char* devname;
 		if ((codec = kmalloc(sizeof(struct ac97_codec), MEMF_KERNEL)) == NULL)
 			return -ENOMEM;
 		memset(codec, 0, sizeof(struct ac97_codec));
@@ -2061,15 +2062,24 @@ static int trident_ac97_init(struct trid
 			codec->codec_write = trident_ac97_set;
 		}
 	
-		if (ac97_probe_codec(codec) == 0)
+		if (ac97_probe_codec(codec) == 0) {
+			kfree(codec);
 			break;
+		}
 
-		if( create_device_node( card->nDeviceID, card->pci_dev->nHandle, "sound/trident/mixer/0", &trident_mixer_fops, codec ) < 0 ) {
+		if ((devname = kmalloc(30,MEMF_KERNEL)) == NULL) {
+			kfree(codec); return -ENOMEM;
+		}
+		strcpy(devname,"sound/trident/mixer/0");
+		devname[strlen(devname)-1] = '0'+num_ac97;
+
+		if( create_device_node( card->nDeviceID, card->pci_dev->nHandle, devname, &trident_mixer_fops, codec ) < 0 ) {
 			printk( "trident: failed to create mixer node \n");
-			kfree(codec);
+			kfree(codec); kfree(devname);
 			break;
 		}
 
+		kfree(devname); /* last component is copied and freed in vfs/dev.c */
 		card->ac97_codec[num_ac97] = codec;
 
 		/* if there is no secondary codec at all, don't probe any more */

-- 
Colin Phipps <cp...@cp...>

Re: [Syllable-kernel] doc patches - submission

[Tim t. L. <ti...@sc...>]

> Thanks Tim, I'll patch & check them in this weekend.  Do you plan on
> documenting other parts of the kernel?

Yes, but currently all my time is used up on a big report for my studies
and on work. Holidays are on the horizon however.

I already got most of swap.c documented, it's quite "interesting" that
either the memory subsystem has some substantial limitations regarding the
sharing of memory, or that the swapcode has a huge bug...

> I'll probably create a doc/ directory within the kernel source tree and drop
> the HTML there.  "make install-doc" can then copy it to E.g.
> /atheos/Documentation/kernel

That's fine. It's both inside the kernel source for people hacking on the
kernel (thus easily updated), and in a central documentation folder so
easy to find for potential kernel developers.

Tim.

Re: [Syllable-kernel] Not receiving posts to the list

[Bram V. D. <bra...@pa...>]

At 16:29 17/06/2004, you wrote:
>This is just a test.  I was looking through the list archives via 
>Sourceforge yesterday and I saw some posts that I have'nt received.  So 
>just hoping this email makes it back to me some how =)

I was having the same problem, but it apparently my spam filter somehow 
went completely insane and was flagging all my mail as spam :/. Fixed now =).

  - Bram 

Re: [Syllable-kernel] doc patches - submission

[Kristian V. D. V. <va...@li...>]

On Thursday 17 June 2004 3:24 pm, Tim ter Laak wrote:
> Finally I've found some time to submit these patches. Thanks go to Brent
> for proofreading them (and making some corrections), all remaining errors
> are of course my own. Vanders, would you apply the patch to CVS and find a
> nice place to put the HTML file?

Thanks Tim, I'll patch & check them in this weekend.  Do you plan on 
documenting other parts of the kernel?

I'll probably create a doc/ directory within the kernel source tree and drop 
the HTML there.  "make install-doc" can then copy it to E.g. 
/atheos/Documentation/kernel

-- 
Vanders
http://syllable.sourceforge.net/
http://www.liqwyd.com

Re: [Syllable-kernel] doc patches - submission

[William H. <me...@wh...>]

On Thursday 17 Jun 2004 15:24, Tim ter Laak wrote:
> Hello,
>
> Finally I've found some time to submit these patches. Thanks go to Brent
> for proofreading them (and making some corrections), all remaining errors
> are of course my own. Vanders, would you apply the patch to CVS and find a
> nice place to put the HTML file?
>
> Tim.

Cool, more documentation is definitely very handy (it helps plebs like me). I 
suspect Brent will add the HTML version to SUB.

Will H

[Syllable-kernel] Not receiving posts to the list

[James H. <jam...@ho...>]

This is just a test.  I was looking through the list archives via 
Sourceforge yesterday and I saw some posts that I have'nt received.  So just 
hoping this email makes it back to me some how =)

Cheers,
James Hayhurst

_________________________________________________________________
Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage! 
http://join.msn.click-url.com/go/onm00200362ave/direct/01/

[Syllable-kernel] doc patches - submission

[Tim t. L. <ti...@sc...>]

Hello,

Finally I've found some time to submit these patches. Thanks go to Brent
for proofreading them (and making some corrections), all remaining errors
are of course my own. Vanders, would you apply the patch to CVS and find a
nice place to put the HTML file?

Tim.

RE: [Syllable-kernel] Task scheduler - compiling the kernel

[Kristian V. <kri...@xe...>]

James Hayhurst wrote:
> Ok, this is just a simple forward of Vanders instructions for 
> compiling the kernel.

Sorry, the list was configured for "Reply to sender" so my mail
went to you directly.  I've changed the list config. so new mails
should be "Reply to list" instead.

--
Vanders
http://www.syllable.org
http://www.liqwyd.com

_____________________________________________________________________
This message has been checked for all known viruses by Xenicom delivered through the MessageLabs Virus Control Centre. 

[Syllable-kernel] Task scheduler - compiling the kernel

[James H. <jam...@ho...>]

Ok, this is just a simple forward of Vanders instructions for compiling the 
kernel.  I more or less just wanted to make sure that Bram and Daniel are 
subscribed here.  Lets all get our Syllable systems to a point where we can 
compile the kernel.  It does'nt take to much horsepower to do that actually, 
it's reasonably fast for me and I'm running under VMware.  Anyways, let me 
know when you guys are ready to rock and the fun will begin.  Let me know if 
you have any probs.

-James

PS - note that you want "makefile.rules" and not "make.rules" as stated 
below =)


>From: Kristian Vandervliet <kri...@xe...>
>To: 'James Hayhurst' <jam...@ho...>
>Subject: RE: [Syllable-kernel] Compiling the kernel
>Date: Wed, 9 Jun 2004 09:32:36 +0100
>
>James Hayhurst wrote:
> > How would I go about doing this? =)
> >
> > I have the developer tools installed (not the lone just
> > released...but I do have GCC 3.3).
>
>At a minimum you need the following tools installed to properly
>compile the kernel:
>
>Gcc-3.3
>Binutils 2.14
>Nasm
>Make
>M4
>
>You'll also need CVS so that you can retrieve the latest headers
>and kernel sources.
>
>You have two options: One is to use Builder.  Install it as per. the
>documentation.  Retrieve the CVS sources:
>
>$ cvs co syllable/system/sys/kernel/kernel
>
>Build it with:
>
>$ cd syllable/system/sys/kernel
>$ build
>
>You can also do it the manual way.  There is a one-time setup you
>need to perform before you can compile the kernel.  The first
>thing to retrieve are the files make.rules and recurse.rules:
>
>$ cvs co syllable/system/make.rules
>$ cvs co syllable/system/recurse.rules
>
>Put them in /usr/src
>
>$ mkdir /usr/src
>$ mv *.rules /usr/src/
>
>Edit /etc/profile and edit/add the following lines:
>
>export ATHEOS_SRC=/usr/src/
>export ATHEOS_INCLUDE_PATH=/ainc/
>
>You'll need to restart your Aterm for those to take effect.
>
>Now get the latest headers and sources from CVS:
>
>$ cvs co syllable/system/sys/include
>$ cvs co syllable/system/sys/kernel/kernel
>
>Update your local headers
>
>$ cp -a syllable/system/sys/include/* /ainc/
>$ for f in `find /ainc/ -name CVS`;do rm -rf $f;done;rm /ainc/?akefile
>
>Now you can build the kernel
>
>$ cd syllable/system/sys/kernel/kernel/
>$ make
>
>--
>Vanders
>http://www.syllable.org
>http://www.liqwyd.com
>
>_____________________________________________________________________
>This message has been checked for all known viruses by Xenicom delivered 
>through the MessageLabs Virus Control Centre.

_________________________________________________________________
Looking to buy a house? Get informed with the Home Buying Guide from MSN 
House & Home. http://coldwellbanker.msn.com/

[Syllable-kernel] Compiling the kernel

[James H. <jam...@ho...>]

How would I go about doing this? =)

I have the developer tools installed (not the lone just released...but I do 
have GCC 3.3).

Cheers,
James

_________________________________________________________________
Getting married? Find great tips, tools and the latest trends at MSN Life 
Events. http://lifeevents.msn.com/category.aspx?cid=married

[Syllable-kernel] Re: [Syllable-developer] Writing a new scheduler

[Daniel G. <da...@fp...>]

I vote we move it to syllable-kernel.

Daniel

On Mon, 2004-06-07 at 16:30 +0000, James Hayhurst wrote:
> Haha ok, well we'll keep it on list then!  You and Daniel convinced me ;o)
> 
> -James
> 
> >But I'm interested in this sort of stuff - e-mailing off list would not 
> >help others learn of successes and mistakes :(
> >
> >>
> >>>We should probably also start emailing off list (?) so I'm not constantly 
> >>>making huge-ass posts =op
> >>
> >>
> >>It's not like Syllable-Dev is all that high-traffic ;).
> >>But alright, feel free to mail me seperately :).
> >
> >--
> >                                                |>>>
> >Dessimat0r                              /`\    |
> >"We cannot turn back time, but we can      _  _|_  _
> >move it forwards with our own hands."     |;|_|;|_|;|
> >                                           \\.    .  /
> >[www:    http://codeknight.net   ]         \\:  .  /
> >[e-mail: des...@nt... ]          ||: U |        /`\
> >[icq:    21477909                ]          ||:.  |
> >[msn:    des...@nt... ]     \,/  ||: U.|
> >                                             ||:   |    \,/
> >                                             ||: , |
> >     ____--`~--- '--~~__            __ ----~ -  ~`---,
> >-~--~                   ~---__ ,--~'                  ~~----___
> >
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by: GNOME Foundation
> >Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> >GNOME Users and Developers European Conference, 28-30th June in Norway
> >http://2004/guadec.org
> >_______________________________________________
> >Syllable-developer mailing list
> >Syl...@li...
> >https://lists.sourceforge.net/lists/listinfo/syllable-developer
> 
> _________________________________________________________________
> MSN Toolbar provides one-click access to Hotmail from any Web page  FREE 
> download! http://toolbar.msn.click-url.com/go/onm00200413ave/direct/01/
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> Syllable-developer mailing list
> Syl...@li...
> https://lists.sourceforge.net/lists/listinfo/syllable-developer

[Syllable-kernel] PCMCIA Support

[daniel m. <dan...@op...>]

Hi I'm new to Syllable and was wondering whether there is any PCMCIA =
support? There are a few laptops listed under the hardware section as =
working in AtheOS....=20

What would be required to get PCMCIA working in Syllable if it is not =
currently working/implemented?

Re: [Syllable-kernel] CPU detection

[Henrik I. <he...@bo...>]

Hi James,

I am cross-posting this reply to the main mailing list, becuse the kernel
list seems very empty... :(

I don't know why the CPU detection fails, maybe someone else can help you
with that.

The source code is not in the distribution, but you can fetch it using
anonymous CVS. Look at the bottom of this page:

http://syllable.sourceforge.net/modules.php?name=Downloads

/Henrik

----- Original Message ----- 
From: "James Hayhurst" <jam...@ho...>
To: <syl...@li...>
Sent: Tuesday, August 19, 2003 10:16 AM
Subject: [Syllable-kernel] CPU detection


> Hey everyone, just got a fresh install of 0.4.5 fro the ISO onto my old
4gig
> HD.  It's cool to be using it for real, instead of clunking along using
> VMware.  So the crux of the matter, Syllable is running on a hand-me-down
> 1.33 Duron system with a Soyo MB (SY-K7ADA V1.0 which has an ALi ALiMAGiK1
> Chipset).
>
> Syllable Manager reports the following for CPU 0:
> Core Speed: 0 MHz
> Bus Speed: 0 MHz
> Features: MMX, MMX2, 3DNow, 3DNowEx, SSE
>
> Not sure if it's the chipset that jacks it up or what, but just thought
I'd
> let u know, I'll see if I can find the source code and poke around
there(is
> it included in the distribution?)
>
> Cheers,
> James
>
> _________________________________________________________________
> <b>MSN 8:</b> Get 6 months for $9.95/month.
> http://join.msn.com/?page=dept/dialup
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Syllable-kernel mailing list
> Syl...@li...
> https://lists.sourceforge.net/lists/listinfo/syllable-kernel
>
>

[Syllable-kernel] CPU detection

[James H. <jam...@ho...>]

Hey everyone, just got a fresh install of 0.4.5 fro the ISO onto my old 4gig 
HD.  It's cool to be using it for real, instead of clunking along using 
VMware.  So the crux of the matter, Syllable is running on a hand-me-down 
1.33 Duron system with a Soyo MB (SY-K7ADA V1.0 which has an ALi ALiMAGiK1 
Chipset).

Syllable Manager reports the following for CPU 0:
Core Speed: 0 MHz
Bus Speed: 0 MHz
Features: MMX, MMX2, 3DNow, 3DNowEx, SSE

Not sure if it's the chipset that jacks it up or what, but just thought I'd 
let u know, I'll see if I can find the source code and poke around there(is 
it included in the distribution?)

Cheers,
James

_________________________________________________________________
<b>MSN 8:</b> Get 6 months for $9.95/month. 
http://join.msn.com/?page=dept/dialup

[Syllable-kernel] Its a new feaure..

[<uda...@lk...>]

well.. Isn't it that the main pupose of this project is to make AtheOS
Filesystem available to linux users as well. I suppose its a feature being
added over to linux. So understanding the other code would also be
important.

regards
udayan






Message: 1
From: "Chris Dennett" <Des...@nt...>
To: <syl...@li...>
Date: Thu, 10 Jul 2003 12:56:37 +0100
Subject: [Syllable-kernel] Re: Syllable-kernel digest, Vol 1 #4 - 1 msg

I agree that it is a good idea to 'reinvent the wheel', it is poor practice
to constantly rely on other projects - sometimes a native FS is very
important.

If you rely upon other projects, where is the innovation?




>
>    1. Understanding for Athos Filesystem (uda...@lk...)
>
> -- __--__--
>
> Message: 1
> To: syl...@li...
> From: uda...@lk...
> Date: Wed, 9 Jul 2003 10:05:06 +0530
> Subject: [Syllable-kernel] Understanding for Athos Filesystem
>
> Hi ..
>
> I have joined a group on Athfs developer group and posted a question
> there..
>
> Question --
> | 1. Whats the main advantage /disadvantage of Atheos Filesystem in
> | comparision to other filesystems on Linux .. lets say Ext3 ?
>
>
> Answer --
> Well, the AtheOS filesystem is actually a virtual filesystem, so along
> with physical files & directories, there are also pipes/fifos, device
> files, etc..  I'm really not the authority on this, certainly you're
> welcome to ask the Syllable <http://syllable.sf.net/> development team.
>
> The main thing about this filesystem is that it's specifically designed
> for Syllable/AtheOS.  Syllable could quite easily use EXT3, and at one
> stage, it was possible to run it on FAT32, but re-inventing the wheel
> can be interesting, hence why this OS uses its own.
>
> The AthFS project is about bringing this filesystem to the Linux kernel,
> mainly to allow people to install Syllable & manipulate AthFS partitions
> from within Linux.
>
>
>
> But out here i m not conviced that its a virtual filesystem . The case
> should be like you can actually load the Atheos Filesystem on Linux
> Machine. As in you can have Amoeba , QNX4.x , etc. Correct me if i m
wrong
> on this.
>
> Next what is the advantage/ disadvantage of AtheOS Filesystem , lets say
> the characteristics of the same.
>
> Where can i find some code/documentation links , that can give me a
better
> idea about the AtheOs Filesystem.
>
> Regards
> Udayan
>
>

[Syllable-kernel] Re: Syllable-kernel digest, Vol 1 #4 - 1 msg

[Chris D. <Des...@nt...>]

I agree that it is a good idea to 'reinvent the wheel', it is poor practice
to constantly rely on other projects - sometimes a native FS is very
important.

If you rely upon other projects, where is the innovation?

----- Original Message ----- 
From: <syl...@li...>
To: <syl...@li...>
Sent: Thursday, July 10, 2003 4:26 AM
Subject: Syllable-kernel digest, Vol 1 #4 - 1 msg


> Send Syllable-kernel mailing list submissions to
> syl...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/syllable-kernel
> or, via email, send a message with subject or body 'help' to
> syl...@li...
>
> You can reach the person managing the list at
> syl...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Syllable-kernel digest..."
>
>
> Today's Topics:
>
>    1. Understanding for Athos Filesystem (uda...@lk...)
>
> --__--__--
>
> Message: 1
> To: syl...@li...
> From: uda...@lk...
> Date: Wed, 9 Jul 2003 10:05:06 +0530
> Subject: [Syllable-kernel] Understanding for Athos Filesystem
>
> Hi ..
>
> I have joined a group on Athfs developer group and posted a question
> there..
>
> Question --
> | 1. Whats the main advantage /disadvantage of Atheos Filesystem in
> | comparision to other filesystems on Linux .. lets say Ext3 ?
>
>
> Answer --
> Well, the AtheOS filesystem is actually a virtual filesystem, so along
> with physical files & directories, there are also pipes/fifos, device
> files, etc..  I'm really not the authority on this, certainly you're
> welcome to ask the Syllable <http://syllable.sf.net/> development team.
>
> The main thing about this filesystem is that it's specifically designed
> for Syllable/AtheOS.  Syllable could quite easily use EXT3, and at one
> stage, it was possible to run it on FAT32, but re-inventing the wheel
> can be interesting, hence why this OS uses its own.
>
> The AthFS project is about bringing this filesystem to the Linux kernel,
> mainly to allow people to install Syllable & manipulate AthFS partitions
> from within Linux.
>
>
>
> But out here i m not conviced that its a virtual filesystem . The case
> should be like you can actually load the Atheos Filesystem on Linux
> Machine. As in you can have Amoeba , QNX4.x , etc. Correct me if i m wrong
> on this.
>
> Next what is the advantage/ disadvantage of AtheOS Filesystem , lets say
> the characteristics of the same.
>
> Where can i find some code/documentation links , that can give me a better
> idea about the AtheOs Filesystem.
>
> Regards
> Udayan
>
>
>
>
>
> --__--__--
>
> _______________________________________________
> Syllable-kernel mailing list
> Syl...@li...
> https://lists.sourceforge.net/lists/listinfo/syllable-kernel
>
>
> End of Syllable-kernel Digest