gbraad's shared items in Google Reader

Django 1.2 released

(author unknown) — Sat, 22 May 2010 20:29:30 PDT

Shared by walkah
sweet :)

It's here!

After many months of work, we're proud to announce the release today of Django 1.2. There's so much cool stuff packed into it that even a summary can't do it justice; you'll just have to go read the release notes to see it all, then swing by the downloads page to grab a copy. And as always, signed checksums for the release package are available.

One important point is worth mentioning here, however: Django 1.2 is, as covered in the release notes, the first official release of Django which does not support Python 2.3. Django still runs on 2.x Python, but the minimum version requirement is now 2.4. Django 1.1, which is still supported with security updates, continues to provide Python 2.3 support if you need it, and will do so until its support lifetime ends with the release of Django 1.3.

Finally, we'd like to point out, as always, that we couldn't do this without the help of the huge numbers of people all around the world who contribute to and improve Django every single day. All of you should give yourselves a big pat on the back, and if you happen to be in Berlin next week, go celebrate with your fellow Djangonauts at DjangoCon EU.

Update: It's been pointed out that the config file which builds the Django documentation didn't get its version number incremented in the Django 1.2 package. To rectify this we're going to wait 24 hours to make sure no other oversights are discovered in 1.2, then issue Django 1.2.1 tomorrow afternoon -- May 18, US Central time -- with an updated documentation builder.

Milkymist project news, May 20th

Sebastien Bourdeauducq, lekernel.net — Thu, 20 May 2010 11:59:55 PDT

UPCOMING PRESENTATIONS
The next months will be busy with events around Milkymist. By chronological order, here is a brief overview of what is going to happen.

It may not be obvious, but for the last two years I’ve been a Master’s student in SoC design at the Royal Institute of Technology in Stockholm. My thesis is about the architecture of the Milkymist SoC, and the seminar will take place on June, 8th, 15:00 in Stockholm, Sweden (full address available soon). The defense seminar is public. The draft report is also available, and, I believe, contains information valuable to many developers.
Back from Stockholm, I will hold a workshop in Paris, France, about writing Milkymist/MilkDrop patches. It will take place at 12:00 on June 20th at the CNAM (292 Rue Saint-Martin 75003 Paris) and is part of a series of hacking workshops happening there on the same day. More information to come.
Wolfgang Spraul will present and hopefully demonstrate the project at Campus Party in Colombia between June 28th and July 6th.
Finally, I will be present at the Rencontres Mondiales du Logiciel Libre (Bordeaux, France) on July 6th to talk about the project.

MILKYMIST ONE
Adam Wang has completed the lay-out of the printed circuit board and has generated the Gerber plots. The design is available online. The PCB design is now out to the manufacturer, and boards should come back in a dozen days (see the schedule page).

Because many people seem to focus exclusively on Milkymist One, I think it is worthwhile to make a quick reminder so they will not be disappointed. What is coming out of the factory in a couple of days really are blank and untested FPGA boards, and nothing else. Porting the existing SoC design to them is likely to take weeks. It’s not like flashing a new board equipped with a proven microcontroller with a well-established OS, it’s about porting an existing SoC design to the bleeding-edge Spartan-6 FPGA technology. We are likely to encounter synthesizer bugs, timing problems, and high-speed I/O issues specifically around the DDR SDRAM. There is also substantial background development to be made (develop a JTAG flasher, modify the NOR flash controller so it supports the M1 chip, design, implement and test a double-data-rate I/O system for the SDRAM compatible with the Spartan-6, etc.). All of this will definitely take time. On top of that, software needs to be developed or improved: the RTEMS port, the Genode FX GUI toolkit and the Flickernoise VJ application. The Milkymist One PCB is only the visible part of the iceberg, really.

MILKYMIST SOC
A 0.5.1 release is around the corner, which consist mostly of bug fixes. Nonetheless, those fixes now enable the correct rendering of 62 (and counting) MilkDrop presets on the Milkymist platform.

Another change has been a rewrite of the SDRAM initialization system, which no longer requires on-chip RAM, and makes it easier to write alternative bootloaders like the port of MicroMonitor Michael Walle has been working on.

WEBSITE
I have changed the website to highlight the three main areas of the project (SoC design, conventional hardware design and embedded VJ software development). Hopefully, it will be more clear to not-so-technical people and will explain to others that Milkymist is not (just) “an FPGA project”.

Nicu Buculei: Fedora at Libre Graphics Meeting

(author unknown) — Thu, 20 May 2010 04:39:00 PDT

This year the Fedora Design Team will have a strong presence at the Libre Graphics Meeting in Brussels, including a presentation about our team and designing with Free tools in an Open community, scheduled on Thursday 27 May 2010 from 17:30 to 18:00. Come to see the awesome presentation (me humble? never!) and meet those ass-kicking guys:

Martin, true hacker and awesome guy, who learn quantum physics, design, code and package for Fedora and also learn Japanese.

The energetic Pierros, charismatic Fedora Ambassador and a new and valuable acquisition of the Design Team.

And lastly, Nicu, the troll that everyone loves to hate (me humble? never!) and one of the old farts in the team.

WE will be there for the entire conference, so even if you can't attend the presentation, come at any time to meet us, talk about stuff and maybe get some design work done. And, most important, drink some fine Belgian beers.

Luke Slater: Not Found

(author unknown) — Sun, 16 May 2010 08:10:37 PDT

The URL you requested could not be found.

Luke Slater: Why I switched to Fedora

(author unknown) — Sun, 16 May 2010 12:49:19 PDT

Since the election is now over and the future of our government must be left to show itself to be effective or not, I thought it would be appropriate to go back to posting about things which don’t make my blood boil (as much), a choice which has attracted outspoken praise from the UK Blood Pressure Society and associated groups.

Like most Linux users who have started in the past few years I began with Ubuntu. However, soon after gaining my “linux-legs” I was off on the road of experimentation, trying every distribution that I could get my livecd-burning hands on. After a while I tended towards Mandriva, because it is a solid distribution with an excellent package manager and wide hardware support; this worked fine for my needs until fairly recently when I got more into using Linux for development-based and work-orientated activities. I found that development was difficult on distributions like Mandriva because of non-standard configurations of software, old packages and just plain broken packages.

On a singular scale these might not be so annoying but when you need to install a set of software packages to create an effective development environment, catering for the oversights in packaging gets tedious and annoying. So after watching fellow developers glide by in their fancy Fedora development machines, I decided to give it a try on my desktop machine.

It works!

That sounds simple enough, but in the world of Linux, “working” just doesn’t come as standard sometimes. The livecd installed it and then after some minor trouble with my two screens (which was my fault for plugging them in the wrong sockets) it just worked. It is also the first distribution I used in which the free graphics driver worked properly, which is also big plus and shows the giant strides that have been made in the development of free drivers in the past few years.

When I installed packages, whether for desktop use or development use, they just worked. I think that the mistake that other distributions make is that they think developers don’t mind compiling things themselves or messing around with things for hours trying to find the right option to prod, but in fact we just want a working base that we can develop our application on. Is that too much to ask? This is not just limited to Mandriva, either, it just happens to be the distribution that I used: the same problems can be found on Sabayon, SuSE and various other distributions.

While I was expecting Fedora to be useful for development, I wasn’t expecting a marked improvement in desktop use. I’m a KDE user and I was a bit wary that since Fedora’s default desktop is GNOME, the implementation may have been a bit hacky but I couldn’t have been more wrong! It’s fast, it’s smooth and everything works.

Though Fedora is fairly brilliant overall, it isn’t all sunshine and smiles (though it is mostly). The feature I miss the most from Mandriva is the integrated control center which makes it much easier to administer the machine. I’m also not sure I like kpackagekit (which is what Fedora KDE uses for its yum front-end), though in reality it’s simple enough to do what it does effectively.

My favourite property of the Fedora project, however, is the fact that it is the first distribution that I have come accross which can truly call itself “community driven” - Putting all the other distributions with similar claims to utter shame in its wake. The whole idea of Fedora is to get the people that use Fedora at whatever level right into helping the project in whatever way they can, and in contrast to a lot of other projects there is plenty to do if you’re not a hard-core developer such as marketing or being an ambassador. Some attribute the success of the community to the directionality given to it by Red Hat but whatever the reason, it’s a great project which is characterised by friendliness and involvement, a project which I look forward to involving myself with duly.

Looking for something a bit better? Try Fedora today!

Commuity News April 29th

vegyraupe — Thu, 29 Apr 2010 01:29:25 PDT

Hey, the second edition of our community news is out. It is divided between news around the Ben NanoNote, SAKC, Milkymistm, OpenWrt and miscellaneous items :)

Ben NanoNote

Xiangfu posted a report on disassembling
David published a video showing the communication between his Ben and an Arduino board

Xiangfu presented a new project – “xbboot” – aimed at replacing the current usbboot as the main tool to reflash the Ben
Ernest Kugel posted he got xburst tools working on Slackware
David created a logo contest for the OpenWrt splash screen
Mirko re-raised the environment / identity partition issue

SAKC

Adam sourced all parts necessary for the next small run of SAKC, and sent a package to Carlos which Carlos already received in Bogota. That includes LCMs, FPGAs, crystals, even some HopeRF modules to play with. Carlos is now waiting for his new PCBs to arrive (currently scheduled for May 5) before starting to mount the next load of SAKC boards. We don’t know yet how many fully working boards we will have in the end, but if you are interested in one please speak up. They will go to people who can contribute back the most…
Carlos reported he has a soft MIPS processor from Open Cores working on SAKC FPGA

Milkymist

Sebastien announced the release of Milkymist 0.5
Sebastien presented new Milkymist Logos and Stickers
Sebastien congratulated Yann on his GSoC project which will serve as a basis for the future OS of Milkymist
Adam finished a first pass of routing of the PCB of the Milkymist One interactive VJ station, currently under review.

OpenWrt

Mirko announced the plan to release different flavors of the uboot, the rootfs as well as the kernel, among them a Debian compatible kernel image

Misc

David announced Tuxbrain was chosen to be one of the representatives of the Open Economy sector in the 20+20 project of Escuela de Organizacion Industrial (Industrial Organization School)
David send a list of events organized by the Spanish copyleft hardware community happening in may
Mirko announced changes in the wiki and Wolfgang gave more details
Wolfgang announced the upgrade of indefero to version 1.0
Wolfgang setup public searchable archives for the #qi-hardware IRC channel on freenode, and all commits into projects at projects.qi-hardware.com will trigger a 1-line commitlog into #qi-hardware as well.

Google Buzz Trick

doghouse — Fri, 12 Feb 2010 00:00:00 PST

Try this at home… And we wanna see it. Post a screenshot of the results here. Immediately!

SPICE support added to upstream qemu

Haydn Solomon — Fri, 16 Apr 2010 06:04:20 PDT

This week saw the first set of SPICE patches introducted to upstream qemu. These are early patches so it’s still unstable but it works good enough to start playing with it. The patches are also dependent on libspice which have not yet been committed so you’ll have to build your own. It’s also interesting to note that the SPICE project now falls under the freedesktop. org project so a lot of the code needed to build the library will be sourced from there. I haven't started playing with this yet but I'll document procedures for getting this up and running in a follow up post.

To see the announcement on the mailing list see the following link.

http://lists.gnu.org/archive/html/qemu-devel/2010-04/msg00967.html

Charlie Brej: Falling blocks game in Plymouth

(author unknown) — Fri, 02 Apr 2010 16:52:13 PDT

So, you have sat down at your computer and you’re waiting for it to boot, then suddenly you realise that it is doing a full fsck which is going to take a few minutes. What to do. You have two options:

Sit quietly watching the little bar move slowly across
Plymouth falling blocks game!

This is not a serious proposal, I just wanted to exercise the scripting system to see if I could find any bugs, but if you want to have a play with it, the script is available.

Chrome+Switchy!+Sock5 (SSH)上网的正确设置

(author unknown) — Mon, 05 Apr 2010 14:51:47 PDT

在Chrome下使用Switchy!+Sock5（SSH/Tor/...)上网的正确设置

随着翻墙运动由城市转向农村，目前使用Chrome+Switchy!+Sock5方式上网的同学越来越多，但是仍然有不少帖子反映无法正常使用代理。

经调试发现，造成不能使用代理的主要原因是Pac中使用了PROXY而不是SOCK5的结果。翻了一下Switchy!的代码，发现要达到目的，必须在手动配置中仅仅设定SOCK的代理，其它项留空，同时选用SOCK5方式。其实目前Chrome已经支持通过SOCK5进行DNS查询^[1].根据本人测试,IE8.0支持通过SOCK5代理方式上网，但仍未支持通过SOCK5进行DNS查询，由于DNS劫持，所以就出现了IE无法直接通过SSH建立的Sock5代理上网的现象，而必须借助Privoxy或Polipo等转换软件然后通过HTTP代理才能达到目的。因此获得正确的域名解析是关键，途径有很多种，最简单的就是在网络连接属性里设置Google的DNS服务器(8.8.8.8 & 8.8.4.4)。

下面给出目前常见的代理设置(Chrome):

1.安装最新版Chrome

2.安装Switchy!扩展^[2]

3.在Switcy!中新建一个Profile,使用的端口取决于你的SOCK5代理(如图)：

4.设置Autoproxy项目提供的名单[http://autoproxy-gfwlist.googlecode.com/svn/trunk/gfwlist.txt]：

5.设置使用的上网方式,非拨号不用选:

6.点击Switchy！图标，选择Auto Switch Mode。至此完毕，测试twitter.com应该能正常访问。否则判断IE中的代理设置是否使用自动PAC方式及其配置文件中的代理是否类似SOCK5 XXX.XXX.XXX.XXX:XX形式。

For IE (对于同样的配置适用于IE8，所以建议将DNS设置为能正常工作的服务器，如Google的8.8.8.8。如果IE下访问失败，请用nslookup或ping等工具检测判断访问目标是否正确的地址，或检查hosts文件是否建立不正确的映射。)

本文在Win7+Chrome5.0.360.4+IE8+Plink0.60.8911下测试通过.

via blisdom@gmail.com's docs

Virt-Manager 0.8.4 Adds new UI Features

Haydn Solomon — Wed, 31 Mar 2010 19:56:19 PDT

Last week saw the latest release of virt-manager , 0.8.4, featuring new user interface additions and functionality. Some of these changes address pain points of previous releases that is obvious to anyone familiar with virt-manager. In this post, I’ll walk through these changes so you know what to expect when you eventually upgrade.

Changing Network Device Models

If you’re familiar with virt-manager, then you’ll know that within the VM details window, there are lots of virtual machine settings that require you to delete and re-create them in order to make any changes. The virt-manager developers recognized this and even listed it on the official development roadmap. One of these settings which required this ‘delete and re-create’ procedure in order to configure is the network device. This is a configuration users probably change on a regular basis, if only to experiment. This release allows you to select from a drop down list of device models, a much improved interface from previous releases. Below shows a snapshot of this new interface.

Import existing Disk

There is now an option when creating a virtual machine which allows you to import an existing disk. This addition essentially sets your new virtual machine to boot from disk first. Personally I find this option redundant as you can also select an existing disk if booting from cdrom when creating a new virtual machine. In fairness to the developers, the option to specify boot order was a recent addition to qemu-kvm so I think this initial interface will change in future. In my opinion, a new virtual machine doesn’t need to boot on configuration. I think there should be an option to not allow the virtual machine to boot on initial creation. Then you would have the option to change boot order and any other tweaks before first boot. Below shows this new option.

Boot Device Order

As mentioned in the previous section, qemu-kvm recently added an option which allows you to specify boot device order. I mentioned this new option in a previous post here. This interface is now exposed to virt-manager and is shown in the snapshot below. I’m confident that the initial virtual machine creation dialog will be updated in future releases of virt-manager to make good use of this option.

Specify Shared Network Device such as Bridges

Virt-manager recently added the ability to configure bridges as described in this recent post. This release now allows you to specify bridges as your network device. You will see this option in two places; one during virtual machine creation and when adding a network device. Below shows the option when adding a network device.

Below shows the option when creating a new virtual machine.

Watchdog Device Support

Qemu allows you to specify a virtual hardware watchdog device. This virtual device is enabled by the guest and must be periodically polled by an agent inside the guest or the guest will be restarted by default. You can specify different actions other than resetting your guest. Options include shutdown, poweroff, pause, debug and none. The shutdown action is not recommended as it requires that your guest respond to ACPI signals which may be unreliable if the guest’s watchdog timer has expired. The two models available are ib700 and i6300esb based on intel’s 6300esb i/o controller hub. The ib700 is the simpler model with a single timer. The i6300esb features a pci-based dual timer watchdog. This configuration is now available in virt-manager and shown in the snapshot below from the “add hardware” dialog.

Virtual Machine Description

One other minor feature is the ability to add a text description of your guest in the details tab under the overview section shown below. I haven’t seen yet where else this information is displayed but it’s good to have this kind of information tied to each guest.

Conclusion

Release 0.8.4 adds more ease of use and functionality to virt-manager making it friendlier for typical use cases at home and small business data centers. It still has a ways to go but it is moving along at a steady pace. Virt-manager is also heavily dependent on projects such as libvirt and ultimately what qemu exposes via command line so it can only do what these projects allow it to. I think virt-manager has a lot of potential as an out of the box gui management tool given it’s underlying technology of python and glade which allows for rapid prototyping and development. Feel free to ask questions and comment on your experience with this release.

Nokia N900 gets Meego Release

(author unknown) — Wed, 31 Mar 2010 13:09:52 PDT

Tilt-Shift Time-Lapse Video of Sumo Wresting

(author unknown) — Wed, 31 Mar 2010 11:08:24 PDT

Shared by gbraad
via @laughingsquid (http://laughingsquid.com/)

PS3, OtherOS and Linux

Karanbir Singh — Mon, 29 Mar 2010 08:26:23 PDT

Sony has announced that the next ps3 firmware update - 3.21 - will no longer support the ability to install and run linux on your ps3's. You can read the full announcement here : http://blog.us.playstation.com/2010/03/28/ps3-firmware-v3-21-update/

This does, ofcourse, only impact the older ps3 units. The newer slimline ps3 units never had support for linux. Keep in mind that this whole idea of new and old is a bit relative. Since its been possible to get the 'older' units at retail outlets all this while - ok, at a much higher prices ( £349 for a 120GB 'fat' ps3 as opposed to the £240 for a 250GB 'slim' ps3 ). But it has been possible to get these machines, and its been possible to use them as Linux hosts.

For a long time I believed these models were still being churned out, in much lower numbers and only retailed through specific vendors. But it seems there has been no 'fat' style ps3 units manufactured by SCE in 2010. Attempts to get info from Sony about this situation have been futile. I just get generic replies that they will get back in touch etc, and that I should get in touch with my local SCE vendor.

How much does this haveto do with IBM's recentish news that they are no longer interested in the Cell platform ( http://www.hpcwire.com/features/Will-Roadrunner-Be-the-Cells-Last-Hurrah-66707892.html ) ? Unless they plan on replacing the platform completely, surely it cant be much work keeping the linux / otheros option open. And I dont buy the argument that its cutting into their sales - if there was a market that large, Sony could just have an alternative box that they would put into the retail stores or even via a specialised vendor.

So where does this leave people who bought and run the ps3's only for the otheros support ? I guess they would need to not upgrade their firmwares for one!

- KB

Original post.

Milkymist One work in progress

Sebastien Bourdeauducq, lekernel.net — Fri, 26 Mar 2010 10:53:22 PDT

Milkymist One board

The global placement of the components of the boards for the Milkymist One interactive VJ station is now done (thanks Adam Wang who is in charge of the placement, routing and sourcing). See the picture above to get an idea of how the board will look like!

Board specifications:

XC6SLX45 Spartan-6 FPGA
128MB 32-bit DDR400 SDRAM
32MB parallel flash
VGA output, 24bpp, up to 140MHz pixel clock
Multi-standard SD video input (PAL/SECAM/NTSC)
AC’97 audio
10/100 Ethernet
Memory card reader that accepts microSD cards
Two connectors that accept USB peripherals
Two DMX512 ports
MIDI IN and MIDI OUT ports
RC5-compatible infrared receiver
RS232 debug port

Facebook Goes After Greasemonkey Script Developer

timothy — Thu, 25 Mar 2010 23:00:00 PDT

palmerj3 writes "The popular Facebook Purity greasemonkey script (now renamed Fluff Buster Purity) has been used by thousands to rid their Facebook feeds from the likes of Mafia Wars, Farmville, and other annoying things. Now, Facebook is threatening the developer of this script. Does Facebook have the right to govern their website's design and functionality once it's in the browser?"

第一个开放版权的硬件的产品 Ben NanoNote上市

Xiangfu Liu — Sun, 21 Mar 2010 16:48:36 PDT

配置:

CPU：336 MHz XBurst Jz4720 MIPS兼容 CPU
显示： 3.0” color TFT
分辨率： 320 x 240， 16.7M color
尺寸 (mm)： 99 x 75 x 17.5 (lid closed)
重量： 126 g (包括电池)
内存： 32MB DRAM
2GB NAND 闪存
mini-USB: USB 2.0 High-Speed Device
外放，内置MIC
耳机接口 (3.5 mm)
SDHC microSD
电池：850mAh Li-ion battery
系统：OPENWRT （GNU/LINUX）

NanoNote 是开放版权(简称开权)的硬件

一但购买了开权硬件的产品，其它关于硬件产品的资料你将一起获得如（原理图，源代码）。我们的使命是：为自由软件开发人员提供一个稳定并达到量产质量的硬件平台，方便自由软件开发人员在上面开发有趣的程序。我们见证过一些硬件不稳定，没有为消费者准备好的例子。那样的开放硬件无法克服不稳定的问题，软件开发总在不停地挣扎，受到硬件不断改动的影响。我们在选择硬件设计时，一方面考虑硬件的稳定性和是否已大量生产，另一方面考虑到它是否开放，是否为自由软件的开发提供保护措施和可能性。在某些情况下，硬件设计的确已经能运行一些 Linux 内核版本，但内核却是过时的，很难去修改内核代码来达到其它的目的。我们让这一过程变得容易。我们的主要承诺是给自由软件开发人员提供稳定，工作，高质量的硬件。有了这一坚实的基础，软件开发人员能将精力放在为终端用户创造出绝优的应用软件上。

我们所有的步骤开始于寻找可以开放并且已经量产的硬件。我们与亚洲的制造商、硬件可以开放的或是能够合作设计开权硬件的公司合作。我们的硬件设计工作的重点是记录这些设计，在开放版权下发布这些设计，然后建立一个协作社区努力来改善设计。这些工作将利用自由软件工具如 KiCAD、 HeeksCAD，并且会以开放版权发布完整的硬件和机械设计。

开权硬件有着很好的前景。在专利系统下，终端用户受制于产品的生命周期。在专利的世界里有一个预定的生命周表－EOL(End Of Life)。届时软件支持会停止，产品的计划会停止。而开权硬件是没有 EOL 的。设计始终为加强和扩展敞开大门;由于运行的是 GPL 的软件，终端用户总是可以自由地为自己和其他人提供帮助支持。硬件的计划是开放的。因为设计是基于开放版权，任何一个有新创意的工程师都可以创建一个新的设计，当然只有那些愿意共享设计的才能享受到这种优势。我们的NanoNote发展计划很简单－循序渐进，不断提高。这确保了软件的开发工作。

NanoNote 应用：

维基百科离线版本，这样你就可以把世界上最大的知识共享库放到你的口袋里。
电子词典 NanoNote 可以运行星际译王，有了星际译王NanoNote 比任何一个电子词典产品的字典都要多。
PDF 阅读器，虽然屏幕有点小。
嵌入式开发实验平台，NanoNote 的所有的文档都是可以自由免费的获得。另外NanoNote 有一个从USB启动的功能，如果你不小心把 NanoNote 刷坏了。你总是可以从USB 启动来修复你的 NanoNote。
自学平台，对于很多刚入门学习 GNU/Linux 的朋友来说不知道怎么下手。有了OPENWRT系统，你只需要输入两个命令等上～1个小时就可以完整的从0开始编译你的嵌入式开发环境。如果是最小化配置NanoNote 的文件系统只有 1.4M。

相关链接：

官方网址：http://www.sharism.cc
官方网上商店：http://www.nanonote.cc
文档相关：http://www.qi-hardware.com
NanoNote 源代码：http://projects.qi-hardware.com/
NanoNote 刷机文件：http://downloads.qi-hardware.com/software/images/Ben_NanoNote_2GB_NAND/
关于购买与使用问题可以发邮件到：discussion@lists.qi-hardware.com
到这里定阅：http://lists.qi-hardware.com/cgi-bin/mailman/listinfo
NANONOTE的QQ群：90586412 欢迎加入。
IRC #qi-hardware@freenode.net
中文BLOG：http://www.openmobilefree.net

维基百科离线版本，这样你就可以把世界上最大的知识共享库放到你的口袋里。

开放小本：Ben NanoNote

黑日白月 — Thu, 18 Mar 2010 12:08:50 PDT

致力于开放硬件的 Qi-hardware 最近发售了在 FOSDEM 2010 上颇受关注的开放硬件微型笔记本： Ben NanoNote。

Ben-nanobook 的详细硬件参数：

336 MHz XBurst Jz4720 MIPS 兼容 CPU
显示器: 3.0 寸彩色 TFT
分辨率: 320 x 240, 16.7M 色
大小 (毫米): 99 x 75 x 17.5 (上盖关闭时)
重量: 126 克 (包括电池)
内存: 32MB DRAM
耳机插孔 (3.5 mm)
SDHC microSD 插槽
850mAh 锂离子电池
2GB NAND 内置闪存
mini-USB 2.0 接口
外放及麦克风
全尺寸 qwerty 键盘

目前 Ben NanoNote 售价 $99 ，配备 OpenWRT Linux 发行版。

英文官方站点（更多截图及购买）

大陆地区淘宝订购

大量真机功能演示（包括 Quake 和 FreeDoom）

奇客资讯相关报道

Engadget 简介

PS: FedoraPeople gbraad 计划撰写一篇介绍开放硬件厂商 Qi-hardware 资讯的专稿，预期将在不久后发布在本站，敬请期待～

Filed under: Gadget | Permalink | Add to del.icio.us | Email this | 29 comments

本 NanoNote 的第一个硬件衍生产品

Xiangfu Liu — Fri, 12 Mar 2010 07:09:13 PST

CC 就是Creative Common 。本 NanoNote 的硬件原理图是以CC-BY-SA协议发布。这个SAKC就是一个最好 CC 应用的例子

先贴图片（我总是喜欢图片）

请大家注意看右下角：

QI-HARDWARE

http://nandnote.cc

SAKC_BOARD RC1 CC-BY-SA 3.0

SAKC 是在Ben NanoNote电路图的基破上设计开发的。这样就省去了很大一部分的设计时间。很快的将产品设计出来。并且 Carlos 用了48 个小时就把所有的组件都焊接到PCB上。而且Ben NanoNote的软件也很容易的就运行在 SAKC 上。只是要对一些特殊功能写一些驱动。

可以想像如果有相当一部分硬件的电路图是以 CC 形式开发的。硬件设计开发成本将大大缩小。也会节省相当一部分硬件设计的投入。

很欺待更多的 NanoNote 的衍生品。别忘了在你的硬件设计图上加上 “ CC-BY-SA “

Milkymist projects at Google Summer of Code

Sebastien Bourdeauducq, lekernel.net — Thu, 25 Mar 2010 04:18:45 PDT

Even though my proposal for Milkymist as a mentoring organization was rejected by Google, there is still the possibility to get Milkymist-related work done through GSoC this year by teaming up with other projects. In particular, QEMU (simulation models for the various Milkymist peripherals), LLVM (LatticeMico32 backend), or SimpleDirectmediaLayer (graphics acceleration support) might be interested. We already have someone who should be working on a RTEMS board support package.

If you are a student interested in both GSoC and Milkymist, contact sebastien dot bourdeauducq aat lekernel dot net or drop by our IRC channel (#milkymist on Freenode). Be quick – the complete application process must be done by April 9th (see Timeline).