Greetings,

Firstly, let me apologize for replying to this list in this way, I
subscribed to the list after this message was posted, so properly responding
by using a straight reply back to the mailing list could not be done.

Now, on the the response...

>If I understand correctly, BlueCat is still vaporware.  Seems I
>recall a June release timeframe.  In the software biz, especially
>in Open Source, I wouldn't rely on any 'birds in the bush'.
>If it currently isn't shipping (and I mean that you can really
>get your hands on a copy, not that it is in some sale's guy's
>price book), then don't count on it showing up at any particular
>time.  This can be frustrating to commercial houses, that expect
>that they can throw money at someone and get them to ship
>features they want.  For Linux, you get whatever is out there,
>and it's not a good idea to make plans based on what someone
>has promised that you have no control over.

We have been shipping BlueCat Linux for the past week. I see boxes and boxes
of it go out the dock every day.

Our efforts towards BlueCat are quite focused, we believe that Linux is the
next big thing and are altering all our efforts towards utilizing our
expertise in real-time and UNIX to support Linux in an embedded, real-time
environment.

>
>Having said that, there are some current players out there,
>Lineo Embedix being one that I know of.  They have a 1.0 release,
>based on Caldera, that you can download to try out.  It's
>still kinda' raw, but the basic stuff is there, and it
>has a nice, small footprint.  Lineo promises to have
>more sophisticated development and configuration tools
>out 'real soon now', but just like the above, I wouldn't
>hold my breath.  They do have a reasonable 84-page PDF
>file that describes how the distro is put together, though.
>Looking through that should give you an idea of how you
>could extend and/or embed the system.
>
>On the other hand, the nice thing about getting such
>broad-based source (the kernel is common across most
>all of the distributions), is that you can either find
>someone else to do enhancements, or you can do them
>yourselves.  Once you have a basic release, like the
>Lineo Embedix or the Linux on a Floppy (LOAF) project,
>then using HOWTOS and similar info, you can figure
>out how to make a FLASH- or net-bootable image, or
>write a specialized device driver for your hardware.
>
>Later, you could adopt someone's more
>sophisticated distro, like BlueCat, if and when it
>becomes ready.  In the meantime, you can make
>significant progress on your own, or with the
>help of similar like-minded embedded developers.
>

I am glad you feel BlueCat is a more sophisticated distribution. With our
eventual goal of offering a deterministic, hard real-time kernel replacement
for Linux, I think you will find it to be overall much superior to a
sub-kernel running above Linux. We will continue to support Linux for
embedded use as well (as in the current release).

Best Regards,
Vik Sohal
[EMAIL PROTECTED]


>Cheers,
>
>-- DaveN
>
>>-----Original Message-----
>>From: Jerry Beckmann [mailto:[EMAIL PROTECTED]]
>>Sent: Tuesday, March 21, 2000 12:15 PM
>>To: [EMAIL PROTECTED]
>>Subject: BlueCat Linux
>>
>>
>>Has anyone used BlueCat linux yet? My compnay is considering it, due to
the
>>price and my pushing towards getting a linux type OS over using Windows
CE.
>>
>>The only requirement that my company has is that we be able to program a
>>visual program and that it can write to a memory device. We have no need
for
>>
>>the hard real time OS's just yet.
>>
>>I also realize that it is pretty much just the RedHat version put in a
>>different box, but we like the option of getting support if we need it,
and
>>I don't think RedHat is likely to have the answers that we would be
seeking,
>>
>>if something came up.  Such as how to make the kernel XIP, or a few other
>>embedded related issues.
>>
>>Thanks for any help you can provide,
>>Jerry
>>[EMAIL PROTECTED]
>>Design Engineer
>>Triad Controls
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>;.



----------------------------------------------------------------------------
----

Best Regards,
Vik Sohal
[EMAIL PROTECTED]

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Alex J Lennon
> Sent: Wednesday, March 29, 2000 8:40 AM
> To: [EMAIL PROTECTED]
> Subject: RE: National Geode/MGx and Linux (sound problems)
>
>
> > > I also have encountered problems with the MediaGX and the OSS/Free
> > > sound drivers. The ALSA drivers seem to work well with the GXm but
> > > I have had problems with sound within a JVM. I wondered what your
> > > suggested work around to the problem is ?
> >
> > Are you talking about the soundblaster emulation in the
> > BIOS using VSA? We have worked very closely with National
> > Semiconductor (for some Geode-related projects) and have
> > figured out that 8-bit sound will not work correctly with
> > the current OSS/Free sb driver (which probably is what
> > your JVM trying to use). The patch is very simple:
> >
> > Look for the part on DMA buffer where it is defined as
> > 64K, change it 32K (or any size less than 64K) and your
> > sb driver will now work for both 16-bit and 8-bit
> > emulation.
> >
> > This is due to some mistakes in VSA code and hopefully
> > NS will release some updated code for BIOS updates.
>
> Thanks Eric / T.J. - Yes it is the soundblaster emulation in the BIOS.
>
> Standard settings of 0x220, 5, 1, 5 except that the MPU401 is disabled
> as the Linux box seems to lock up with it enabled.
>
> The CPU is the MediaGX-233 with 5530 companion. I'm not sure about the
> VSA code version but I think it is the latest worker that was available
> from Cyrix back before NS took over.
>
> I am including sound support as modules (soundcore, soundlow, sound,
> uart401, sb)
> The MPU401 I/O base is not specified to the command line of sb.o and the
> source
> seems to show that it defaults to disabled.
>
> I did the mod. to 'sound_config.h' as you suggested and changed the
> DSP_BUFFSIZE
> from 64Kb to 32Kb (also tried 16Kb). Recompiled the modules (Kernel
> 2.2.12-20) and
> updated my LinuxBox with sb.o, sound.o, uart401.o.
>
> I checked that the DMA buffer sizes had actually changed with
> some printk()
> messaging.
>
> Unfortuately XMMS under GNOME (for example) is still playing .WAV
> files with
> lots of
> buzzing/clicking.
>
> I wondered if there are any obvious mistakes in the above - or if you had
> any other thoughts ?
>
> Thanks again,
>
> Alex
>
>
> --
> To unsubscribe from this list, send a message to [EMAIL PROTECTED]
> with the command "unsubscribe linux-embedded" in the message body.
> For more information, see <http://waste.org/mail/linux-embedded>.
>
BEGIN:VCARD
VERSION:2.1
N:Sohal;Vik
FN:Vik Sohal
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20000322T235256Z
END:VCARD

Reply via email to