From info at martenvijn.nl Wed Apr 1 10:57:47 2009 From: info at martenvijn.nl (Marten Vijn) Date: Wed Apr 1 10:57:53 2009 Subject: thin accesspoint controler In-Reply-To: <1238502445.8635.322.camel@mvn-desktop> References: <1238502445.8635.322.camel@mvn-desktop> Message-ID: <1238608664.6436.48.camel@mvn-desktop> On Tue, 2009-03-31 at 14:27 +0200, Marten Vijn wrote: > Hi, > > Is there a away in FreeBSD, to use accesspoints > like "thin accesspoints" controled by a controler unit. > I just found out that i am probably reffering to CAPWAP http://www.ietf.org/html.charters/capwap-charter.html Is anyone aware of developments in FreeBSD? kind regards, Marten -- http://martenvijn.nl Marten Vijn http://martenvijn.nl/trac/wiki/soas Sugar on a Stick http://bsd.wifisoft.org/nek/ The Network Event Kit http://har2009.org 13th-16th August http://opencommunitycamp.org 26th Jul - 2nd August From andrew at fubar.geek.nz Sat Apr 4 23:08:34 2009 From: andrew at fubar.geek.nz (Andrew Turner) Date: Sat Apr 4 23:08:46 2009 Subject: FreeBSD NAND flash driver Message-ID: <20090405175014.6aef7016@fubar.geek.nz> I've been working on a FreeBSD NAND flash driver and NAND simulator [1]. I have tested reading and writing to the simulated NAND device but not erasing. It is not usable yet as the write will not perform any deletes from the device, either the file system or another geom will have to issue a BIO_DELETE followed by BIO_WRITE's to write to the disk. This is done to support NAND flash aware file systems. TODO: * ECC support. * Add GEOM attributes to get information about the NAND device out, eg. Block size, OOB data, etc. * Test the erase code. * Add support for real hardware. * Read the parameter page on parts that support it to get the required information. Andrew [1] http://fubar.geek.nz/files/freebsd/nand/freebsd-nand-20090405.tar.gz From andrew at fubar.geek.nz Sun Apr 5 13:58:16 2009 From: andrew at fubar.geek.nz (Andrew Turner) Date: Sun Apr 5 13:58:29 2009 Subject: FreeBSD NAND flash driver In-Reply-To: References: <20090405175014.6aef7016@fubar.geek.nz> Message-ID: <20090406085808.1fba0aa4@fubar.geek.nz> On Sun, 05 Apr 2009 14:57:10 +0200 Ivan Voras wrote: > Andrew Turner wrote: > > I've been working on a FreeBSD NAND flash driver and NAND simulator > > [1]. I have tested reading and writing to the simulated NAND device > > but not erasing. > > Hi, > > Have you seen this: > http://lists.freebsd.org/pipermail/freebsd-arch/2009-April/009146.html ? Yes. As I had written most of the code already I felt it would be better to release it now than during the middle of the Summer of Code so if the student is accepted they could work on the existing code base rather than duplicating work I have already done. There is still a lot of work to do on the driver before it is usable including getting it working on real hardware. Andrew From stas at FreeBSD.org Mon Apr 6 01:24:18 2009 From: stas at FreeBSD.org (Stanislav Sedov) Date: Mon Apr 6 01:24:27 2009 Subject: FreeBSD NAND flash driver In-Reply-To: <20090405175014.6aef7016@fubar.geek.nz> References: <20090405175014.6aef7016@fubar.geek.nz> Message-ID: <20090406122410.daab24b3.stas@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 5 Apr 2009 17:50:14 +1200 Andrew Turner mentioned: > I've been working on a FreeBSD NAND flash driver and NAND simulator [1]. > I have tested reading and writing to the simulated NAND device but not > erasing. Great news! > It is not usable yet as the write will not perform any deletes from the > device, either the file system or another geom will have to issue > a BIO_DELETE followed by BIO_WRITE's to write to the disk. This is done > to support NAND flash aware file systems. > So, for ordinary file systems we're going to use the special geom layer that will sit above the nand(8) device and perform BIO_DELETE operations when required? > TODO: > * ECC support. > * Add GEOM attributes to get information about the NAND device out, > eg. Block size, OOB data, etc. > * Test the erase code. > * Add support for real hardware. > * Read the parameter page on parts that support it to get the required > information. > > Andrew > > [1] http://fubar.geek.nz/files/freebsd/nand/freebsd-nand-20090405.tar.gz What about putting this information to the wiki? Seems like a good start for anyone who'll be working on the real hardware. And thanks again for the great work! - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAknZvC4ACgkQK/VZk+smlYFgGQCeP/sXZcjhEBrvHQtdcO+iPC6R yKoAnisUV9Jmfagx4sQCcE5wWGABI/y0 =cmW/ -----END PGP SIGNATURE----- !DSPAM:49d9bc2e967004191370449! From bugmaster at FreeBSD.org Mon Apr 6 04:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 6 04:07:34 2009 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200904061106.n36B6ppE061821@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/15876 embedded [picobsd] PicoBSD message of the day problems 4 problems total. From andrew at fubar.geek.nz Mon Apr 6 04:26:03 2009 From: andrew at fubar.geek.nz (Andrew Turner) Date: Mon Apr 6 04:26:17 2009 Subject: FreeBSD NAND flash driver In-Reply-To: <20090406122410.daab24b3.stas@FreeBSD.org> References: <20090405175014.6aef7016@fubar.geek.nz> <20090406122410.daab24b3.stas@FreeBSD.org> Message-ID: <20090406232508.776d57e6@fubar.geek.nz> On Mon, 6 Apr 2009 12:24:10 +0400 Stanislav Sedov wrote: > > It is not usable yet as the write will not perform any deletes from > > the device, either the file system or another geom will have to > > issue a BIO_DELETE followed by BIO_WRITE's to write to the disk. > > This is done to support NAND flash aware file systems. > > > > So, for ordinary file systems we're going to use the special geom > layer that will sit above the nand(8) device and perform BIO_DELETE > operations when required? Yes, this is intentional as NAND flash is split up to blocks. The blocks are then split into pages. You have to erase the entire block at a time but can write pages as required. A file system that knows about this difference will be able to talk to nand(8) directly. > > > TODO: > > * ECC support. > > * Add GEOM attributes to get information about the NAND device out, > > eg. Block size, OOB data, etc. > > * Test the erase code. > > * Add support for real hardware. > > * Read the parameter page on parts that support it to get the > > required information. > > > > Andrew > > > > [1] > > http://fubar.geek.nz/files/freebsd/nand/freebsd-nand-20090405.tar.gz > > What about putting this information to the wiki? Seems like a good > start for anyone who'll be working on the real hardware. > And thanks again for the great work! I'm planning on doing this. I'm currently cleaning up the code before getting the first hardware driver written. Andrew From aragon at phat.za.net Mon Apr 6 07:21:54 2009 From: aragon at phat.za.net (Aragon Gouveia) Date: Mon Apr 6 07:22:00 2009 Subject: FreeBSD NAND flash driver In-Reply-To: <20090406232508.776d57e6@fubar.geek.nz> References: <20090405175014.6aef7016@fubar.geek.nz> <20090406122410.daab24b3.stas@FreeBSD.org> <20090406232508.776d57e6@fubar.geek.nz> Message-ID: <49DA0BD6.5080303@phat.za.net> Hi, Andrew Turner wrote: > Yes, this is intentional as NAND flash is split up to blocks. The > blocks are then split into pages. You have to erase the entire block at > a time but can write pages as required. A file system that knows about > this difference will be able to talk to nand(8) directly. What I know about file systems and UFS is pretty limited, so forgive me if what follows are silly questions. Are there any defragmentation routines in UFS that could/should be disabled when using it on a flash device? I know a file system can be optimized for space or time with tunefs(8). I imagine optimizing for space would be best for a flash device? Is there anything else other than that and your work that can improve flash support? Thanks, Aragon From cyrkon at gazeta.pl Wed Apr 8 06:00:29 2009 From: cyrkon at gazeta.pl (cyrkon Gazeta.pl) Date: Wed Apr 8 06:00:36 2009 Subject: Named and NanoBSD on FreeBSD 7.1 Message-ID: <48c928460904080539g75f85ad0v4e6e696d5ad186ae@mail.gmail.com> Hello! I can not create my own named.conf file... When I create /etc/namedb/named.conf, edit it, then copy to /cfg (mount /cfg, cp /etc/namedb/named.conf /cfg/namedb/, umount /cfg) and restart; aftr restart /etc/namedb/named.conf has old ("default") content. Anyone can help, please? From ganbold at micom.mng.net Wed Apr 8 09:41:41 2009 From: ganbold at micom.mng.net (Ganbold) Date: Wed Apr 8 09:41:49 2009 Subject: FreeBSD NAND flash driver In-Reply-To: <20090406232508.776d57e6@fubar.geek.nz> References: <20090405175014.6aef7016@fubar.geek.nz> <20090406122410.daab24b3.stas@FreeBSD.org> <20090406232508.776d57e6@fubar.geek.nz> Message-ID: <49DCC26D.8060008@micom.mng.net> Andrew Turner wrote: >> What about putting this information to the wiki? Seems like a good >> start for anyone who'll be working on the real hardware. >> And thanks again for the great work! >> > I'm planning on doing this. I'm currently cleaning up the code before > getting the first hardware driver written. > I have Intel turbo memory in my laptop, so if you need some testing please let me know. thanks, Ganbold > Andrew > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" > > > > -- Your education begins where what is called your education is over. From karoslu at gmail.com Wed Apr 8 13:01:11 2009 From: karoslu at gmail.com (=?Big5?B?p2arVL3l?=) Date: Wed Apr 8 13:27:15 2009 Subject: 2nd CFP: The 2009 International Workshop on Reconfigurable and Multi-core Embedded Systems (WoRMES'2009) Message-ID: <4baea8fa0904081231h11dc3b0ek8248d910195b84a7@mail.gmail.com> ---------------------------- WoRMES'2009 Call for Papers ---------------------------- The 2009 International Workshop on Reconfigurable and Multi-core Embedded Systems (WoRMES'2009) http://embedded.cs.ccu.edu.tw/WoRMES2009 to be held conjunction with The 2009 IEEE/IFIP International Conference on Embedded and Ubiquitous Computing (EUC'2009) http://cse.stfx.ca/~euc09/ August 29-31 2009, Vancouver, Canada ---------------------------------------------------------------------------------------------------- INTRODUCTION ----------------------- With the progress and popularization of embedded systems in the past few years, efficiency, instead of functionalities, has become an important factor in measuring the value of embedded systems. How to efficiently use the limited resources in an embedded system to obtain optimal performance has also become a very important issue. Reconfigurable and multi-core architectures are promising solutions to this issue. TOPICS ---------- The WoRMES'2009 workshop provides a forum for discussing the state-of-the-art in reconfigurable computing technologies and multi-core embedded systems and also encourages researchers to publish their experiences in reconfigurable computing technologies, multi-core embedded systems, and the integration of the two research areas. The researchers can share their research result in a comfortable and relaxed environment, and then get some feedback to improve their research and advance the development of reconfigurable computing technologies and multi-core embedded systems. Topics include but are not limited to? * Reconfigurable Hardware Architectures * Run-time Resource Management of Reconfigurable Hardware * Operating Systems for Reconfigurable Embedded Systems * Application Design for Reconfigurable Embedded Systems * Dynamic Partial Reconfiguration Techniques * Programming Models for Reconfigurable Systems * Multi-core Operating Systems and Scheduling * Hardware Designs for Multi-core Architectures * Multi-core Application Design * Programming Models for Embedded Multi-core Architectures * Reconfigurable Multi-core Architecture Design * Reconfigurable Multi-core SoC Implementation IMPORTANT DATES --------------------------- Submission deadline: April 15, 2009 Authors Notification: May 25, 2009 Final Manuscript Due: June 15, 2009 Workshop: August 29-31, 2009 PAPER SUBMISSION and PUBLICATION ----------------------------------------------------- Prepare the paper with either MS-Word or LaTeX. The max number of pages is 6, plus 2 extra pages to be purchased if necessary. The paper should be submitted in the PDF format. Full papers should be submitted through the submission system: http://embedded.cs.ccu.edu.tw/WoRMES2009/submission. The accepted papers will be published by IEEE Computer Society Press as a separate proceeding (indexed by EI). Selected papers, after further revisions, will be invited for inclusion in a special issue of the International Journal of Embedded Systems (IJES), Inderscience Publishers. NOTIFICATION --------------------- Submitting a paper to the workshop mean that, if the paper is accepted, at least one author should attend the workshop and present the paper. For no-show authors, their papers will be removed from the digital library after the conference and their affiliations will be notified. ORGANIZATION ----------------------- Program Chairs: Pao-Ann Hsiung, National Chung Cheng University, Taiwan Chun-Hsien Lu, National Chung Cheng University, Taiwan Program Committee: See WoRMES'2009 web site: http://embedded.cs.ccu.edu.tw/WoRMES2009 For further information regarding the workshop and paper submission, please contact with General: wormes@embedded.cs.ccu.edu.tw Program: Pao-Ann Hsiung (pahsiung@cs.ccu.edu.tw) Chun-Hsien Lu (lch96p@cs.ccu.edu.tw) From mike at sentex.net Wed Apr 8 14:01:13 2009 From: mike at sentex.net (Mike Tancsa) Date: Wed Apr 8 14:01:20 2009 Subject: Named and NanoBSD on FreeBSD 7.1 In-Reply-To: <48c928460904080539g75f85ad0v4e6e696d5ad186ae@mail.gmail.co m> References: <48c928460904080539g75f85ad0v4e6e696d5ad186ae@mail.gmail.com> Message-ID: <200904082038.n38KcBxu087107@lava.sentex.ca> At 08:39 AM 4/8/2009, cyrkon Gazeta.pl wrote: >Hello! >I can not create my own named.conf file... >When I create /etc/namedb/named.conf, edit it, then copy to /cfg >(mount /cfg, cp /etc/namedb/named.conf /cfg/namedb/, umount /cfg) and >restart; aftr restart /etc/namedb/named.conf has old ("default") >content. >Anyone can help, please? Is there one on /conf/base/etc/namedb thats killing your copy ? ---Mike From mailing at gaturkey.com Thu Apr 9 00:46:17 2009 From: mailing at gaturkey.com (Global Access Travel) Date: Thu Apr 9 00:47:20 2009 Subject: Private Shore Excursions-Turkey Message-ID: [http://www.turkeycalling.us] PRIVATE SHORE EXCURSIONS- TURKEY Your cruise clients will make the best of their time in Turkey on a private shore excursion! Istanbul Kusadasi & Ephesus [mailto:incoming@gaturkey.com?subject=Private Shore Excursions- Turkey] **************************************************************************** Yasal Uyar?; Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir, yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve sisteminizden siliniz. Global Turizm Hizmetleri Anonim Sirketi bu mesajin icerigi ile ilgili olarak hicbir hukuksal sorumlulugu kabul etmez. **************************************************************************** Disclaimer; This e-mail communication is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and that may not be made public by law or agreement. If the recipient of this message is not the intended recipient or entity, you are hereby notified that any further dissemination, distribution or copying of this information is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete it from your system. The Global Turizm Hizmetleri Anonim Sirketi does not accept legal responsibility for the contents of this message. *********************************************************************************************** Yasal Uyar?; Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir, yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve sisteminizden siliniz. Global Turizm Hizmetleri Anonim Sirketi bu mesajin icerigi ile ilgili olarak hicbir hukuksal sorumlulugu kabul etmez. ********************************************************************************************** Disclaimer; This e-mail communication is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and that may not be made public by law or agreement. If the recipient of this message is not the intended recipient or entity, you are hereby notified that any further dissemination, distribution or copying of this information is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete it from your system. The Global Turizm Hizmetleri Anonim Sirketi does not accept legal responsibility for the contents of this message. This message was sent by: Global Access Incoming, Nuzhetiye cad, istanbul, besiktas 34357, Turkey Powered by iContact: http://freetrial.icontact.com To be removed click here: http://app.icontact.com/icp/mmail-mprofile.pl?r=46043310&l=82228&s=DG7B&m=562566&c=305227 Forward to a friend: http://app.icontact.com/icp/sub/forward?m=562566&s=46043310&c=DG7B&cid=305227 From andrew at fubar.geek.nz Thu Apr 9 04:23:18 2009 From: andrew at fubar.geek.nz (Andrew Turner) Date: Thu Apr 9 04:23:26 2009 Subject: FreeBSD NAND flash driver In-Reply-To: <49DCC26D.8060008@micom.mng.net> References: <20090405175014.6aef7016@fubar.geek.nz> <20090406122410.daab24b3.stas@FreeBSD.org> <20090406232508.776d57e6@fubar.geek.nz> <49DCC26D.8060008@micom.mng.net> Message-ID: <20090409232310.27c2fae0@fubar.geek.nz> On Wed, 08 Apr 2009 23:27:41 +0800 Ganbold wrote: > Andrew Turner wrote: > >> What about putting this information to the wiki? Seems like a good > >> start for anyone who'll be working on the real hardware. > >> And thanks again for the great work! > >> > > I'm planning on doing this. I'm currently cleaning up the code > > before getting the first hardware driver written. > > > > I have Intel turbo memory in my laptop, so if you need some testing > please let me know. The Intel Turbo memory appears to be based on the Non-Volatile Memory Host Controller Interface [1]. The NAND driver talks directly to devices that approximate the ONFI spec so the NAND driver wouldn't be able to talk to the Intel Turbo memory as far as I can tell. Andrew [1] http://www.intel.com/standards/nvmhci/index.htm [2] http://onfi.org/ From bugmaster at FreeBSD.org Mon Apr 13 04:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 13 04:33:21 2009 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200904131106.n3DB6oWf084899@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/15876 embedded [picobsd] PicoBSD message of the day problems 4 problems total. From karoslu at gmail.com Wed Apr 15 11:18:31 2009 From: karoslu at gmail.com (=?Big5?B?p2arVL3l?=) Date: Wed Apr 15 12:42:19 2009 Subject: WoRMES'09 CFP: Deadline extension to April 29, 2009 Message-ID: <4baea8fa0904151118x12d1f93ke163b96dddc305fc@mail.gmail.com> ---------------------------- WoRMES'2009 Call for Papers ---------------------------- Deadline Extension The 2009 International Workshop on Reconfigurable and Multi-core Embedded Systems (WoRMES'2009) http://embedded.cs.ccu.edu.tw/WoRMES2009 to be held conjunction with The 2009 IEEE/IFIP International Conference on Embedded and Ubiquitous Computing (EUC'2009) http://cse.stfx.ca/~euc09/ August 29-31 2009, Vancouver, Canada ---------------------------------------------------------------------------------------------------- DEADLINE EXTENSION Submission deadline: April 15, 2009 Extended for 2 weeks: April 29, 2009 ---------------------------------------------------------------------------------------------------- INTRODUCTION ----------------------- With the progress and popularization of embedded systems in the past few years, efficiency, instead of functionalities, has become an important factor in measuring the value of embedded systems. How to efficiently use the limited resources in an embedded system to obtain optimal performance has also become a very important issue. Reconfigurable and multi-core architectures are promising solutions to this issue. TOPICS ---------- The WoRMES'2009 workshop provides a forum for discussing the state-of-the-art in reconfigurable computing technologies and multi-core embedded systems and also encourages researchers to publish their experiences in reconfigurable computing technologies, multi-core embedded systems, and the integration of the two research areas. The researchers can share their research result in a comfortable and relaxed environment, and then get some feedback to improve their research and advance the development of reconfigurable computing technologies and multi-core embedded systems. Topics include but are not limited to? * Reconfigurable Hardware Architectures * Run-time Resource Management of Reconfigurable Hardware * Operating Systems for Reconfigurable Embedded Systems * Application Design for Reconfigurable Embedded Systems * Dynamic Partial Reconfiguration Techniques * Programming Models for Reconfigurable Systems * Multi-core Operating Systems and Scheduling * Hardware Designs for Multi-core Architectures * Multi-core Application Design * Programming Models for Embedded Multi-core Architectures * Reconfigurable Multi-core Architecture Design * Reconfigurable Multi-core SoC Implementation IMPORTANT DATES --------------------------- Submission deadline (new): April 29, 2009 Authors Notification: May 25, 2009 Final Manuscript Due: June 15, 2009 Workshop: August 29-31, 2009 PAPER SUBMISSION and PUBLICATION ----------------------------------------------------- Prepare the paper with either MS-Word or LaTeX. The max number of pages is 6, plus 2 extra pages to be purchased if necessary. The paper should be submitted in the PDF format. Full papers should be submitted through the submission system: http://embedded.cs.ccu.edu.tw/WoRMES2009/submission. The accepted papers will be published by IEEE Computer Society Press as a separate proceeding (indexed by EI). Selected papers, after further revisions, will be invited for inclusion in a special issue of the International Journal of Embedded Systems (IJES), Inderscience Publishers. NOTIFICATION --------------------- Submitting a paper to the workshop mean that, if the paper is accepted, at least one author should attend the workshop and present the paper. For no-show authors, their papers will be removed from the digital library after the conference and their affiliations will be notified. ORGANIZATION ----------------------- Program Chairs: Pao-Ann Hsiung, National Chung Cheng University, Taiwan Chun-Hsien Lu, National Chung Cheng University, Taiwan Program Committee: See WoRMES'2009 web site: http://embedded.cs.ccu.edu.tw/WoRMES2009 For further information regarding the workshop and paper submission, please contact with General: wormes@embedded.cs.ccu.edu.tw Program: Pao-Ann Hsiung (pahsiung@cs.ccu.edu.tw) Chun-Hsien Lu (lch96p@cs.ccu.edu.tw) From security at jim-liesl.org Thu Apr 16 15:47:22 2009 From: security at jim-liesl.org (security) Date: Thu Apr 16 16:34:48 2009 Subject: tinybsd- ports question Message-ID: <49E7AF2B.2020908@jim-liesl.org> I'm using fbsd 7.1-p4. (running under qemu/kqemu/windows host) question: When I build a tinybsd image (wrap), it rebuilds all the ports every time I run it. All the ports already have been built on the build system. Am I missing something here? I thought it checked to see if the ports were already installed, and if so, it copied the binaries (and extras) rather than building them fresh every time. I'm really torn between nano and tiny. I like nano's ability to skip the world and kernel builds and the "extra" boot partition. Tiny has a much more elegant ports handler and is smart about getting the world binaries from the host. Tiny needs less space, but with flash getting so cheap, it's less of an important factor for me. I do realize other embedded uses might find that more important. thanks jim From matthias-bsde at mteege.de Fri Apr 17 01:21:34 2009 From: matthias-bsde at mteege.de (Matthias Teege) Date: Fri Apr 17 02:08:50 2009 Subject: nanobsd boot slice selection does not work Message-ID: <635bff4620629cdcaa016cca98d50389@mteege.de> Moin, I have problems with the bootslice selection on a soekris device. I use updatepX to copy new images to the device but after a reboot the old slice is mountet as root. I boot the device from slice 1, updatep2, reboot the device, "2" is selected in the bootmanager but ads1a is mounted as root. After selecting "2" with keyboard on the console it works. After that I can reboot the device without any problems and slice 2 is mounted as root. I can reproduce this problem with different CF Cards. Does anyone know this problem? Can I force the bootslice selection? My testdevice is a 4801 with comBIOS ver. 1.31 20070408 the system is FreeBSD 7.2pre. Many thanks Matthias From fb-embedded at psconsult.nl Fri Apr 17 04:16:36 2009 From: fb-embedded at psconsult.nl (Paul Schenkeveld) Date: Fri Apr 17 04:56:30 2009 Subject: nanobsd boot slice selection does not work In-Reply-To: <635bff4620629cdcaa016cca98d50389@mteege.de> References: <635bff4620629cdcaa016cca98d50389@mteege.de> Message-ID: <20090417104848.GA919@psconsult.nl> On Fri, Apr 17, 2009 at 09:49:21AM +0200, Matthias Teege wrote: > Moin, > > I have problems with the bootslice selection on a soekris device. I use > updatepX to copy new images to the device but after a reboot the old > slice is mountet as root. > > I boot the device from slice 1, updatep2, reboot the device, "2" is > selected in the bootmanager but ads1a is mounted as root. After selecting > "2" with keyboard on the console it works. After that I can reboot the > device without any problems and slice 2 is mounted as root. > > I can reproduce this problem with different CF Cards. Does anyone know > this problem? Can I force the bootslice selection? > > My testdevice is a 4801 with comBIOS ver. 1.31 20070408 the system is > FreeBSD 7.2pre. I've done many nanobsd installs on net4801 with FreeBSD up to 7.1p3 and never come across this problem. The switch of the default boot slice is made by updatepX calling boot0cfg but only after all preceding steps (notably dd of the image and fsck of the newly installed image) were successful. Did you see correct output from dd and fsck at the end of the updatepX run? What does 'boot0cfg -v ad0' tell you (change ad0 to you flash device if different)? Manual selection of the default boot slice can be done with: # boot0cfg -v -s X ad0 where X is the desired slice (1 or 2) and ad0 is the name of your flash device. I'll see if I can do the test with 7.2pre or 7.2rc1 this weekend. Regards, Paul Schenkeveld From matthias-bsde at mteege.de Fri Apr 17 05:58:27 2009 From: matthias-bsde at mteege.de (Matthias Teege) Date: Fri Apr 17 06:20:59 2009 Subject: nanobsd boot slice selection does not work In-Reply-To: <20090417104848.GA919@psconsult.nl> Message-ID: <0c9e7e64a8be8ddaf12a27ab43dbbf8c@mteege.de> Moin, > Did you see correct output from dd and fsck at the end of the updatepX > run? Yes, no error message. > What does 'boot0cfg -v ad0' tell you (change ad0 to you flash device if > different)? # boot0cfg -v ad1 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5 494: 15:32 32 253408 2 0x80 495: 1: 1 0xa5 989: 15:32 253472 253408 3 0x00 990: 0: 1 0xa5 993: 15:32 506880 2048 version=1.0 drive=0x80 mask=0x3 ticks=182 bell=# (0x23) options=packet,update,nosetdrv default_selection=F2 (Slice 2) reboot with slice 2, works # boot0cfg -s 1 -v ad1 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5 494: 15:32 32 253408 2 0x80 495: 1: 1 0xa5 989: 15:32 253472 253408 3 0x00 990: 0: 1 0xa5 993: 15:32 506880 2048 version=1.0 drive=0x80 mask=0x3 ticks=182 bell=# (0x23) options=packet,update,nosetdrv default_selection=F1 (Slice 1) reboot with slice 2 to, but shows "Boot: 1" in Bootmanager. If I select "1" with keyboard/console it boots from slice 1. If I select "2" with the keyboard it boots from slice 2. It autoboots the slice which was last selected by keyboard. It doesn't matter which slice I select with boot0cfg. Many thanks Matthias From richard at unixguru.nl Fri Apr 17 10:07:04 2009 From: richard at unixguru.nl (Richard Arends) Date: Fri Apr 17 10:33:12 2009 Subject: tinybsd- ports question In-Reply-To: <49E7AF2B.2020908@jim-liesl.org> References: <49E7AF2B.2020908@jim-liesl.org> Message-ID: <20090417094407.GP238@shell.unixguru.nl> On Thu, Apr 16, 2009 at 03:20:27PM -0700, security wrote: Jim, > I'm using fbsd 7.1-p4. (running under qemu/kqemu/windows host) > > question: When I build a tinybsd image (wrap), it rebuilds all the ports > every time I run it. All the ports already have been built on the build > system. Am I missing something here? I thought it checked to see if > the ports were already installed, and if so, it copied the binaries (and > extras) rather than building them fresh every time. The tinybsd ports are built within a chroot'ed environment and indeed not copied from the base host. -- Regards, Richard. /* Homo Sapiens non urinat in ventum */ From bms at incunabulum.net Sat Apr 18 01:22:57 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Sat Apr 18 05:16:40 2009 Subject: tinybsd- ports question In-Reply-To: <49E7AF2B.2020908@jim-liesl.org> References: <49E7AF2B.2020908@jim-liesl.org> Message-ID: <49E989B9.8080007@incunabulum.net> security wrote: > I'm really torn between nano and tiny. I like nano's ability to skip > the world and kernel builds and the "extra" boot partition. Tiny has a > much more elegant ports handler and is smart about getting the world > binaries from the host. Tiny needs less space, but with flash getting > so cheap, it's less of an important factor for me. I do realize other > embedded uses might find that more important. > [general hand waving] The fact that TinyBSD copies binaries from the host was always what caused me to side-step it; try doing that on a non-i386 machine, or for a non-i386 target. Having said that, it would be really cool if someone could blend the strengths of both into NanoBSD... surely the ports stuff is not too difficult to merge in? The only thing really missing which is needed, sadly, is cross-compilation support -- but you can spend years doing that. OpenEmbedded certainly isn't an answer. You don't need to rebuild everything in NanoBSD at once if you don't want to. cheers BMS From mah at jump-ing.de Sat Apr 18 13:06:10 2009 From: mah at jump-ing.de (Markus Hitter) Date: Sat Apr 18 13:09:13 2009 Subject: tinybsd- ports question In-Reply-To: <49E989B9.8080007@incunabulum.net> References: <49E7AF2B.2020908@jim-liesl.org> <49E989B9.8080007@incunabulum.net> Message-ID: <5412CA0D-A6E7-4318-BD6E-9BC60CC07446@jump-ing.de> Am 18.04.2009 um 10:05 schrieb Bruce Simpson: > The fact that TinyBSD copies binaries from the host was always what > caused me to side-step it; try doing that on a non-i386 machine, or > for a non-i386 target. > > Having said that, it would be really cool if someone could blend > the strengths of both into NanoBSD... How about not using a chrooted environment, but a whole virtual machine? You can build the TinyBSD host exactly like you need the binaries on your target and then extract the essentials for the boot image. Works like a charme here, speeds up debugging a lot and raises the question why support for ports was added at all. Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ From imp at bsdimp.com Sat Apr 18 15:44:32 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Apr 18 15:44:39 2009 Subject: tinybsd- ports question In-Reply-To: <49E989B9.8080007@incunabulum.net> References: <49E7AF2B.2020908@jim-liesl.org> <49E989B9.8080007@incunabulum.net> Message-ID: <20090418.094323.1723177110.imp@bsdimp.com> In message: <49E989B9.8080007@incunabulum.net> Bruce Simpson writes: : security wrote: : > I'm really torn between nano and tiny. I like nano's ability to skip : > the world and kernel builds and the "extra" boot partition. Tiny has a : > much more elegant ports handler and is smart about getting the world : > binaries from the host. Tiny needs less space, but with flash getting : > so cheap, it's less of an important factor for me. I do realize other : > embedded uses might find that more important. : > : : [general hand waving] : The fact that TinyBSD copies binaries from the host was always what : caused me to side-step it; try doing that on a non-i386 machine, or for : a non-i386 target. I have patches that make this work, except for one thing. It doesn't do the shared library dependencies however, since ldd doesn't work on non-native architectures. : Having said that, it would be really cool if someone could blend the : strengths of both into NanoBSD... surely the ports stuff is not too : difficult to merge in? The only thing really missing which is needed, : sadly, is cross-compilation support -- but you can spend years doing : that. OpenEmbedded certainly isn't an answer. Both NanoBSD and TinyBSD can do cross building. However, the problem is that this cross building only works for the base system. Ports need some help... Warner From bugmaster at FreeBSD.org Mon Apr 20 11:06:50 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 20 11:07:36 2009 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200904201106.n3KB6nJF032970@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/15876 embedded [picobsd] PicoBSD message of the day problems 4 problems total. From nick at van-laarhoven.org Mon Apr 20 13:51:43 2009 From: nick at van-laarhoven.org (Nick Hibma) Date: Mon Apr 20 13:51:51 2009 Subject: nanobsd boot slice selection does not work In-Reply-To: <0c9e7e64a8be8ddaf12a27ab43dbbf8c@mteege.de> References: <0c9e7e64a8be8ddaf12a27ab43dbbf8c@mteege.de> Message-ID: <200904201535.21191.nick@van-laarhoven.org> I've seen this problem as well, but can't for the life of me remember what I did about it. Searching in our build environment does not yield an answer. Does changing boot image options change something? Or change to boot0sio. perhaps the fact that there is no keyboard confuses things. Good luck. Nick > Moin, > > > Did you see correct output from dd and fsck at the end of the updatepX > > run? > > Yes, no error message. > > > What does 'boot0cfg -v ad0' tell you (change ad0 to you flash device if > > different)? > > # boot0cfg -v ad1 > # flag start chs type end chs offset size > 1 0x00 0: 1: 1 0xa5 494: 15:32 32 253408 > 2 0x80 495: 1: 1 0xa5 989: 15:32 253472 253408 > 3 0x00 990: 0: 1 0xa5 993: 15:32 506880 2048 > > version=1.0 drive=0x80 mask=0x3 ticks=182 bell=# (0x23) > options=packet,update,nosetdrv > default_selection=F2 (Slice 2) > > reboot with slice 2, works > > # boot0cfg -s 1 -v ad1 > # flag start chs type end chs offset size > 1 0x00 0: 1: 1 0xa5 494: 15:32 32 253408 > 2 0x80 495: 1: 1 0xa5 989: 15:32 253472 253408 > 3 0x00 990: 0: 1 0xa5 993: 15:32 506880 2048 > > version=1.0 drive=0x80 mask=0x3 ticks=182 bell=# (0x23) > options=packet,update,nosetdrv > default_selection=F1 (Slice 1) > > reboot with slice 2 to, but shows "Boot: 1" in Bootmanager. > > If I select "1" with keyboard/console it boots from slice 1. If I select > "2" with the keyboard it boots from slice 2. It autoboots the slice which > was last selected by keyboard. It doesn't matter which slice I select > with boot0cfg. > > Many thanks > Matthias > > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to > "freebsd-embedded-unsubscribe@freebsd.org" From matthias-bsde at mteege.de Mon Apr 20 13:55:28 2009 From: matthias-bsde at mteege.de (Matthias Teege) Date: Mon Apr 20 13:55:34 2009 Subject: nanobsd boot slice selection does not work In-Reply-To: <200904201535.21191.nick@van-laarhoven.org> Message-ID: <4b925570b9c69698b6eb029454ed29fa@mteege.de> Moin, > I've seen this problem as well, but can't for the life of me remember what I I'm relieved to hear that. > did about it. Searching in our build environment does not yield an answer. I use fdisk to set the active slice as workaround. > Does changing boot image options change something? I don't think so. I've changed update/noupdate, packet/nopacket, setdrv/nosetdrv without any success. > Or change to boot0sio. perhaps the fact that there is no keyboard confuses > things. I use boot0sio all the time. I is the default in nanobsd. # grep boot0sio /usr/src/tools/tools/nanobsd/nanobsd.sh NANO_BOOTLOADER="boot/boot0sio" I can reproduce the problem under KVM Emulation so I think it isn't a soekris or CF problem. The problem is, that boot0cfg doesn't change the flag for the active slice. In my example slice 2 is always flagged as active. Many thanks Matthias From nick at van-laarhoven.org Mon Apr 20 14:44:42 2009 From: nick at van-laarhoven.org (Nick Hibma) Date: Mon Apr 20 14:44:48 2009 Subject: nanobsd boot slice selection does not work In-Reply-To: <4b925570b9c69698b6eb029454ed29fa@mteege.de> References: <4b925570b9c69698b6eb029454ed29fa@mteege.de> Message-ID: <200904201644.35430.nick@van-laarhoven.org> Moguh, The only reference to booting problems I can find is the following svn log message: "Note: Do NOT use the 'noupdate' option to boot0cfg as this disables the selection of the boot partition through 'boot0cfg -s ...' due to a bug in boot0.S ." The diff suggests that I needed to revert a previous commit because it didn't work as advertised. Perhaps the problem was related to the BIOS version? I've used 1.28 - 1.33 succesfully now. Cheers, Nick > Moin, > > > I've seen this problem as well, but can't for the life of me remember > > what I > > I'm relieved to hear that. > > > did about it. Searching in our build environment does not yield an > > answer. > > I use fdisk to set the active slice as workaround. > > > Does changing boot image options change something? > > I don't think so. I've changed update/noupdate, packet/nopacket, > setdrv/nosetdrv without any success. > > > Or change to boot0sio. perhaps the fact that there is no keyboard > > confuses things. > > I use boot0sio all the time. I is the default in nanobsd. > > # grep boot0sio /usr/src/tools/tools/nanobsd/nanobsd.sh > NANO_BOOTLOADER="boot/boot0sio" > > I can reproduce the problem under KVM Emulation so I think it isn't > a soekris or CF problem. The problem is, that boot0cfg doesn't change > the flag for the active slice. In my example slice 2 is always flagged > as active. > > Many thanks > Matthias From nick at van-laarhoven.org Tue Apr 21 20:39:38 2009 From: nick at van-laarhoven.org (Nick Hibma) Date: Tue Apr 21 20:39:45 2009 Subject: nanobsd boot slice selection does not work In-Reply-To: <200904201644.35430.nick@van-laarhoven.org> References: <4b925570b9c69698b6eb029454ed29fa@mteege.de> <200904201644.35430.nick@van-laarhoven.org> Message-ID: <200904212239.28189.nick@van-laarhoven.org> Well, This is really surprising. It just happened to me today. I found the following workaround if boot0cfg -s 2 ad0 does not boot the second slice. Use echo 'a 2' | fdisk -f /dev/stdin ad0 boot0cfg -s 2 ad0 instead. Cheers, Nick > Moguh, > > The only reference to booting problems I can find is the following svn > log message: > > "Note: Do NOT use the 'noupdate' option to boot0cfg as this disables the > selection of the boot partition through 'boot0cfg -s ...' due to a bug > in boot0.S ." > > The diff suggests that I needed to revert a previous commit because it > didn't work as advertised. > > Perhaps the problem was related to the BIOS version? I've used 1.28 - > 1.33 succesfully now. > > Cheers, > > Nick > > > Moin, > > > > > I've seen this problem as well, but can't for the life of me remember > > > what I > > > > I'm relieved to hear that. > > > > > did about it. Searching in our build environment does not yield an > > > answer. > > > > I use fdisk to set the active slice as workaround. > > > > > Does changing boot image options change something? > > > > I don't think so. I've changed update/noupdate, packet/nopacket, > > setdrv/nosetdrv without any success. > > > > > Or change to boot0sio. perhaps the fact that there is no keyboard > > > confuses things. > > > > I use boot0sio all the time. I is the default in nanobsd. > > > > # grep boot0sio /usr/src/tools/tools/nanobsd/nanobsd.sh > > NANO_BOOTLOADER="boot/boot0sio" > > > > I can reproduce the problem under KVM Emulation so I think it isn't > > a soekris or CF problem. The problem is, that boot0cfg doesn't change > > the flag for the active slice. In my example slice 2 is always flagged > > as active. > > > > Many thanks > > Matthias From info at rickvanderzwet.nl Thu Apr 23 22:01:38 2009 From: info at rickvanderzwet.nl (Rick van der Zwet) Date: Thu Apr 23 22:01:44 2009 Subject: nanobsd image boot issues Message-ID: <5aaae08a0904231438v5b655056g8852dc11f1e83987@mail.gmail.com> Boot delay and fail issues on various hardware using nanobsd generated RELENG_7_1 images on a sandisk 2gb CF (SDCFH2-002G). For example while trying to run a image on a soekris net4521 (bios 1.33) it seems to take ages (up to a minute) to start booting. Same image supplied to a PC (intel Pentium 1 & award bios) using a CF->IDE converter does not seems to boot at all, neither does a net4801 (bios 1.33). Just seems trying to find a boot loader. The net4801 even bails out after a while. Output of fdisk of image list as follows: Disk: /dev/disk3 geometry: 992/64/63 [4001760 sectors] Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ *1: A5 0 1 1 - 491 15 63 [ 63 - 495873] FreeBSD 2: A5 492 1 1 - 983 15 63 [ 495999 - 495873] FreeBSD 3: A5 984 0 1 - 992 15 63 [ 991872 - 9072] FreeBSD 4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused A reference pfSense image put on the same CF card is boot perfectly fine under the net4521 & PC (untested net4801): Disk: /dev/rdisk3 geometry: 992/64/63 [4001760 sectors] Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ 1: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused *4: A5 0 0 1 - 1023 254 63 [ 0 - 50000] FreeBSD Which makes me wonder about the sector start, why does nanobsd not start at sector 0, but uses sector 63 as a start instead. Could that be the explanation or is something else going on? /Rick -- http://rickvanderzwet.nl From imp at bsdimp.com Thu Apr 23 22:26:29 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Apr 23 22:26:35 2009 Subject: nanobsd image boot issues In-Reply-To: <5aaae08a0904231438v5b655056g8852dc11f1e83987@mail.gmail.com> References: <5aaae08a0904231438v5b655056g8852dc11f1e83987@mail.gmail.com> Message-ID: <20090423.162427.-1543901316.imp@bsdimp.com> In message: <5aaae08a0904231438v5b655056g8852dc11f1e83987@mail.gmail.com> Rick van der Zwet writes: : Boot delay and fail issues on various hardware using nanobsd generated : RELENG_7_1 images on a sandisk 2gb CF (SDCFH2-002G). For example while : trying to run a image on a soekris net4521 (bios 1.33) it seems to : take ages (up to a minute) to start booting. Same image supplied to a : PC (intel Pentium 1 & award bios) using a CF->IDE converter does not : seems to boot at all, neither does a net4801 (bios 1.33). Just seems : trying to find a boot loader. The net4801 even bails out after a : while. Output of fdisk of image list as follows: : : Disk: /dev/disk3 geometry: 992/64/63 [4001760 sectors] : Signature: 0xAA55 : Starting Ending : #: id cyl hd sec - cyl hd sec [ start - size] : ------------------------------------------------------------------------ : *1: A5 0 1 1 - 491 15 63 [ 63 - 495873] FreeBSD : 2: A5 492 1 1 - 983 15 63 [ 495999 - 495873] FreeBSD : 3: A5 984 0 1 - 992 15 63 [ 991872 - 9072] FreeBSD : 4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused : This looks right... : A reference pfSense image put on the same CF card is boot perfectly : fine under the net4521 & PC (untested net4801): : : Disk: /dev/rdisk3 geometry: 992/64/63 [4001760 sectors] : Signature: 0xAA55 : Starting Ending : #: id cyl hd sec - cyl hd sec [ start - size] : ------------------------------------------------------------------------ : 1: 00 0 0 0 - 0 0 0 [ 0 - 0] unused : 2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused : 3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused : *4: A5 0 0 1 - 1023 254 63 [ 0 - 50000] FreeBSD This looks like the 'faked' DD geometry. : Which makes me wonder about the sector start, why does nanobsd not : start at sector 0, but uses sector 63 as a start instead. Could that : be the explanation or is something else going on? Because the first cylinder is reserved for the boot blocks. Have you enabled packet mode for boot in boot0 with boot0cfg? Warner From bugmaster at FreeBSD.org Mon Apr 27 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 27 11:07:36 2009 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200904271106.n3RB6puB002233@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/15876 embedded [picobsd] PicoBSD message of the day problems 4 problems total. From karoslu at gmail.com Mon Apr 27 08:45:44 2009 From: karoslu at gmail.com (=?Big5?B?p2arVL3l?=) Date: Mon Apr 27 11:31:09 2009 Subject: Final CFP: The 2009 International Workshop on Reconfigurable and Multi-core Embedded Systems (WoRMES'2009) Message-ID: <4baea8fa0904270145v5f9c914bg35b61ee721c2001c@mail.gmail.com> ------------------------ WoRMES'2009 Call for Papers -------------------------- The 2009 International Workshop on Reconfigurable and Multi-core Embedded Systems (WoRMES'2009) http://embedded.cs.ccu.edu.tw/WoRMES2009 to be held conjunction with The 2009 IEEE/IFIP International Conference on Embedded and Ubiquitous Computing (EUC'2009) http://cse.stfx.ca/~euc09/ August 29-31 2009, Vancouver, Canada ------------------------------------------------------------------------------------------ Submission deadline: April 29, 2009 ------------------------------------------------------------------------------------------ INTRODUCTION ----------------------- With the progress and popularization of embedded systems in the past few years, efficiency, instead of functionalities, has become an important factor in measuring the value of embedded systems. How to efficiently use the limited resources in an embedded system to obtain optimal performance has also become a very important issue. Reconfigurable and multi-core architectures are promising solutions to this issue. TOPICS ---------- The WoRMES'2009 workshop provides a forum for discussing the state-of-the-art in reconfigurable computing technologies and multi-core embedded systems and also encourages researchers to publish their experiences in reconfigurable computing technologies, multi-core embedded systems, and the integration of the two research areas. The researchers can share their research result in a comfortable and relaxed environment, and then get some feedback to improve their research and advance the development of reconfigurable computing technologies and multi-core embedded systems. Topics include but are not limited to? * Reconfigurable Hardware Architectures * Run-time Resource Management of Reconfigurable Hardware * Operating Systems for Reconfigurable Embedded Systems * Application Design for Reconfigurable Embedded Systems * Dynamic Partial Reconfiguration Techniques * Programming Models for Reconfigurable Systems * Multi-core Operating Systems and Scheduling * Hardware Designs for Multi-core Architectures * Multi-core Application Design * Programming Models for Embedded Multi-core Architectures * Reconfigurable Multi-core Architecture Design * Reconfigurable Multi-core SoC Implementation IMPORTANT DATES --------------------------- Submission deadline (new): April 29, 2009 Authors Notification: May 25, 2009 Final Manuscript Due: June 15, 2009 Workshop: August 29-31, 2009 PAPER SUBMISSION and PUBLICATION ----------------------------------------------------- Prepare the paper with either MS-Word or LaTeX. The max number of pages is 6, plus 2 extra pages to be purchased if necessary. The paper should be submitted in the PDF format. Full papers should be submitted through the submission system: http://embedded.cs.ccu.edu.tw/WoRMES2009/submission. The accepted papers will be published by IEEE Computer Society Press as a separate proceeding (indexed by EI). Selected papers, after further revisions, will be invited for inclusion in a special issue of the International Journal of Embedded Systems (IJES), Inderscience Publishers. NOTIFICATION --------------------- Submitting a paper to the workshop mean that, if the paper is accepted, at least one author should attend the workshop and present the paper. For no-show authors, their papers will be removed from the digital library after the conference and their affiliations will be notified. ORGANIZATION ----------------------- Program Chairs: Pao-Ann Hsiung, National Chung Cheng University, Taiwan Chun-Hsien Lu, National Chung Cheng University, Taiwan Program Committee: See WoRMES'2009 web site: http://embedded.cs.ccu.edu.tw/WoRMES2009 For further information regarding the workshop and paper submission, please contact with General: wormes@embedded.cs.ccu.edu.tw Program: Pao-Ann Hsiung (pahsiung@cs.ccu.edu.tw) Chun-Hsien Lu (lch96p@cs.ccu.edu.tw)