Sure It would. Only thing is that, PC output is stereo, so you'll need two ADC channels (already on the pSoC chip) to convert the analog outs into digital and xfer them to other side. However, the actual sampling rate (and hence audio quality) would be limited my bluetooth bandwidth.
For 16bit 44.1kHz stereo you'd need 1.411 Mbit/s speed... I'm not sure whether bluetooth can go upto that speeds. Though, for headphones, lower bit rates/sampling rate should not cause sigificant loss in quality (headphone speakers are already sucky) but would surely help making it feasible project
May be their stress was on purely pSoC based systems (No. 1 doesn't have any other semiconductor device than pSoC). Even if it was this, they should have mentioned this in their competition.
I all my impression is that creativity and effort has been brushed aside in this competition.
Netmeeting has a remote window/desktop feature. It can let people in a meeting give control of applications running on their computer to other people. So, you can show your boss an excel chart, he may change the graph types, modify values etc... All as if the application were running locally.
Yeah PPC is support as a target not as a development platform. You can install QNX RTP, then make a target buildfile for your PPC with all stuff you want and go!
The only hitch! though OS runtimes are available for PPC target, you'll need to recompile the applications you need for PPC target. Thus even though its just a straight recompile on QNX, but you need to have the sources.
>> 1) The filesystem is as slow as molasses. and other blah
ext2fs is a PIG (just as all else of Linux stuff!). Robustness is the thing embedded system filesystems are designed with in mind. The filesystem drivers are deterministic in nature. Infact each and every core driver is deterministic and overned by realtime execution rules. In an ext2fs, if you loose a few superblocks in badblocks you're doomed. In qnx even if you loose most of it, you can still recover most of the data. Because every critical portion has a magic identifier. Reliability is what matters in an atomic reactor (that's like where QNX is being used!) than a filesystem that gives 27MB/s one day, and bombs (:P) the other day!
And man, does it need to have a journaling filesystem, if it checks and corrects my 10 GB partition in under 20 seconds! (don't wipe your eyes, its correct!). while in lab I administer no *nix does it in 5 mins. also talking about NTFS (a journaling fs), W2K takes around 5 mins to check entire 6GB volume for inconsistencies.
Infact that's why I made a QNX boot image for myself with mandatory disk checking after mount (yep! after mount;) )
I suggest you to take a few readings on qnx.com about realtime OS and you'll know what does it take to make a realtime OS.
Well, yeah.
That floppy demo is QNX4 demo, the old and not-free-even-for-non-commercial-use.
the one showed here is QNX 6.1, which has a gorgeous GUI and runs on a lot of processors. Get it yourself free-for-non-commercial-use at get.qnx.com!
Sure !
QNX has a native networking in addition to TCP/IP. Using this you can turn a group of computers connected via network into a cluster running mathcad or whatever. You can as well run mathcad on a huge computer and see its display on your iPaq (no its not X)
--
Keep Smiling
- mritunjai
And man there is more to QNX...
1) transparent networking: so your desktop computer and your iPaq become one machine! you can control GUI, audio, applications (even run and kill) from any on any machine.
2) fault tolerant OS
3) Micro kernel: no kernel mode drivers. You can kill off everything including HDD drivers, network, and filesystem. just leaving a shell and console driver, and can get back to a full GUI playing MP3's. So if anything goes down, the system still ain't dead!
And please! don't tell me that M$ too lets you know the architecture and philosophy behind the OS and how exactly it does Realtime execution. Plus, You don't get to develop on a desktop class gracious OS and transfer it as it is to target.
You can test/debug/compile your realtime progs on an x86 listening to MP3's (Yeah! everything is prioritised!) and when you're satisfied, compile it for arm,sh-8, or whatever. The screenshots you saw were almost direct ports of the stuff existing for QNX RTP desktop OS!
Slashdot Mirror
QNX Realtime OS supports HyperThreading since Sep 2002. Till now only Xeon had hyperthreading.
For 16bit 44.1kHz stereo you'd need 1.411 Mbit/s speed... I'm not sure whether bluetooth can go upto that speeds. Though, for headphones, lower bit rates/sampling rate should not cause sigificant loss in quality (headphone speakers are already sucky) but would surely help making it feasible project
eg. See this Ultra sonic mapper which does all what the No. 1 does plus MUCH more, and Geeky Keep-in-touch device.
May be their stress was on purely pSoC based systems (No. 1 doesn't have any other semiconductor device than pSoC). Even if it was this, they should have mentioned this in their competition.I all my impression is that creativity and effort has been brushed aside in this competition.
Regards
- Mritunjai
Netmeeting has a remote window/desktop feature. It can let people in a meeting give control of applications running on their computer to other people. So, you can show your boss an excel chart, he may change the graph types, modify values etc... All as if the application were running locally.
Yeah PPC is support as a target not as a development platform. You can install QNX RTP, then make a target buildfile for your PPC with all stuff you want and go!
The only hitch! though OS runtimes are available for PPC target, you'll need to recompile the applications you need for PPC target. Thus even though its just a straight recompile on QNX, but you need to have the sources.
--Keep Smiling
- mritunjai
>> 1) The filesystem is as slow as molasses. and other blah
;) )
ext2fs is a PIG (just as all else of Linux stuff!). Robustness is the thing embedded system filesystems are designed with in mind. The filesystem drivers are deterministic in nature. Infact each and every core driver is deterministic and overned by realtime execution rules. In an ext2fs, if you loose a few superblocks in badblocks you're doomed. In qnx even if you loose most of it, you can still recover most of the data. Because every critical portion has a magic identifier. Reliability is what matters in an atomic reactor (that's like where QNX is being used!) than a filesystem that gives 27MB/s one day, and bombs (:P) the other day!
And man, does it need to have a journaling filesystem, if it checks and corrects my 10 GB partition in under 20 seconds! (don't wipe your eyes, its correct!). while in lab I administer no *nix does it in 5 mins. also talking about NTFS (a journaling fs), W2K takes around 5 mins to check entire 6GB volume for inconsistencies.
Infact that's why I made a QNX boot image for myself with mandatory disk checking after mount (yep! after mount
I suggest you to take a few readings on qnx.com about realtime OS and you'll know what does it take to make a realtime OS.
Well, yeah. That floppy demo is QNX4 demo, the old and not-free-even-for-non-commercial-use.
the one showed here is QNX 6.1, which has a gorgeous GUI and runs on a lot of processors. Get it yourself free-for-non-commercial-use at get.qnx.com!
Sure ! QNX has a native networking in addition to TCP/IP. Using this you can turn a group of computers connected via network into a cluster running mathcad or whatever. You can as well run mathcad on a huge computer and see its display on your iPaq (no its not X) -- Keep Smiling - mritunjai
And man there is more to QNX... 1) transparent networking: so your desktop computer and your iPaq become one machine! you can control GUI, audio, applications (even run and kill) from any on any machine. 2) fault tolerant OS 3) Micro kernel: no kernel mode drivers. You can kill off everything including HDD drivers, network, and filesystem. just leaving a shell and console driver, and can get back to a full GUI playing MP3's. So if anything goes down, the system still ain't dead!
If you've seen CE on a iPaq, you'd know what "gracious" means when you look at the screenshots
Man, at first take a look how the jitters etc are looked into and how OS deals with them. Read the following articles Concepts of Time - I, Concepts of Time- II and What is Realtime.
And please! don't tell me that M$ too lets you know the architecture and philosophy behind the OS and how exactly it does Realtime execution. Plus, You don't get to develop on a desktop class gracious OS and transfer it as it is to target.
You can test/debug/compile your realtime progs on an x86 listening to MP3's (Yeah! everything is prioritised!) and when you're satisfied, compile it for arm,sh-8, or whatever. The screenshots you saw were almost direct ports of the stuff existing for QNX RTP desktop OS!