Re: SMALL FreeBSD capable board
On Aug 5, 2012, at 8:36 AM, Wojciech Puchar wrote: > i am looking for SMALL and specifically low power board that can run from > battery, can run FreeBSD and have at least one ethernet and one USB port, and > reasonable amount of memory (32MB at least). > WiFi not needed. some more than few MB flash is, as well as about 10 GPIO > ports or useful SPI port. > > I already see a lot of useful supported ones in source tree, with ARM and > MIPS. > > I want to make portable router PLUS my own add own hardware, and have full > control over software running on it. > > Any recommendation. > > Ethernut 5 seems great > http://www.ethernut.de/en/hardware/enut5/index.html > > but no info about price and availability in Poland You're looking at about $250 or EU 200 for that. I'd recommend something like: http://www.glomationinc.com/product_9G20u.html which is US$55 + shipping. A friend got one too and will be building an alarm clock out of it (complicated one). http://www.mini-box.com/pico-SAM9G45-X which is US$69, but has a 4 week lead time. I have both of these on order. NAND isn't yet supported, but is high on my Atmel hit list. Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
pmc warnings on stable/9
I have no idea the significance, or danger. When compiling on stable/9 I have always seen the following WARNINGS. Can we silence/fix these? Or is it supposed to be that way? :-) WARNING: hwpmc_soft.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_pmc.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_rwlock.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_sx.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_lock.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_intel.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_tsc.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_amd.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_clock.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_mutex.c: enum pmc_event has too many values: 1531 > 1023 WARNING: trap.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_x86.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_uncore.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_piv.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_core.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_logging.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_mod.c: enum pmc_event has too many values: 1531 > 1023 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
ctfconvert failure on stable/9
Not sure what to make of this error: ERROR: ctfconvert: rc = 2 No entry found [dwarf_next_cu_header(57)] my kernel is compiling, but I seem to fail at understanding something? Sean ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: pmc warnings on stable/9
On Tue, Aug 7, 2012 at 7:16 PM, Sean Bruno wrote: > I have no idea the significance, or danger. When compiling on stable/9 > I have always seen the following WARNINGS. Can we silence/fix these? > Or is it supposed to be that way? :-) > > WARNING: hwpmc_soft.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_pmc.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_rwlock.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_sx.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_lock.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_intel.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_tsc.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_amd.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_clock.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_mutex.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: trap.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_x86.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_uncore.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_piv.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_core.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_logging.c: enum pmc_event has too many values: 1531 > > 1023 > WARNING: hwpmc_mod.c: enum pmc_event has too many values: 1531 > 1023 > > > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" These warnings(and the previous one from your other thread) both come from ctfconvert. I haven't looked into them in detail but I suspect that the CTF format is not able to represent things like enums with more than 1024 entries, or structures with more than a certain number of members. I've never seen any actual side-effects of the warnings, although I suspect that if you tried to use DTrace to examine variables with the affected types you wouldn't be able to inspect everything. As far as I know, DTrace is the only consumer of CTF data in the kernel. I have dreams of replacing DTrace's usage of CTF with libdwarf, but that's little more than idle musings on my part at this stage. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: pmc warnings on stable/9
On Tue, Aug 7, 2012 at 4:37 PM, Ryan Stone wrote: > On Tue, Aug 7, 2012 at 7:16 PM, Sean Bruno wrote: >> I have no idea the significance, or danger. When compiling on stable/9 >> I have always seen the following WARNINGS. Can we silence/fix these? >> Or is it supposed to be that way? :-) >> >> WARNING: hwpmc_soft.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_pmc.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_rwlock.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_sx.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_lock.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_intel.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_tsc.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_amd.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_clock.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_mutex.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: trap.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_x86.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_uncore.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_piv.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_core.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_logging.c: enum pmc_event has too many values: 1531 > >> 1023 >> WARNING: hwpmc_mod.c: enum pmc_event has too many values: 1531 > 1023 >> >> >> ___ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > > These warnings(and the previous one from your other thread) both come > from ctfconvert. I haven't looked into them in detail but I suspect > that the CTF format is not able to represent things like enums with > more than 1024 entries, or structures with more than a certain number > of members. I've never seen any actual side-effects of the warnings, > although I suspect that if you tried to use DTrace to examine > variables with the affected types you wouldn't be able to inspect > everything. As far as I know, DTrace is the only consumer of CTF data > in the kernel. > > I have dreams of replacing DTrace's usage of CTF with libdwarf, but > that's little more than idle musings on my part at this stage. > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" FYI - r207578 added this warning to FreeBSD's ctf, specifically to handle the large pmc_entry enumeration. http://svnweb.freebsd.org/base?view=revision&revision=207578 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Published paper
Hi, I have recently published a paper related to Operating System, can you please check it out http://www.ijcsi.org/papers/IJCSI-9-4-1-77-84.pdf and tell me your opinion, looking forward to hear from you ? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [maybe spam] Published paper
On 8/7/12 5:24 PM, ali mousa wrote: Hi, I have recently published a paper related to Operating System, can you please check it out http://www.ijcsi.org/papers/IJCSI-9-4-1-77-84.pdf and tell me your opinion, looking forward to hear from you ? Certainly interesting.. I will read more of it later. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Published paper
On Tue, Aug 07, 2012 at 17:24:37 -0700 , ali mousa wrote: > Hi, > > I have recently published a paper related to Operating System, can you > please check it out http://www.ijcsi.org/papers/IJCSI-9-4-1-77-84.pdf > and tell me your opinion, looking forward to hear from you ? The DragonFlyBSD project may also find this interesting, because AFAIR one of the reasons Matt forked FreeBSD was due to disagreements in the SMP implementation. -- Thanks and best regards, Chris Nehren pgpf2mA8W83Os.pgp Description: PGP signature
