Developer Welcome

From The Neuros Technology Wiki

Welcome to Neuros Development

Contents 1 The Platform : Neuros OSD 1.1 OSD 1.0 1.2 OSD 2.0 2 The Resources 2.1 Neuros Development Wiki 2.2 IRC 2.3 Mailing List (Google Groups) 2.4 Web 2.5 Bug Tracking 2.6 Source Control 3 The People 4 FAQ

[edit] The Platform : Neuros OSD

[edit] OSD 1.0

Neuros is a company and community building open electronic devices. We have focused on preparing the first product based on a platform with Neuros Linux built on a dual core Texas Instruments Multimedia DM320 Processor: the Neuros OSD.

There is a whole portal page dedicated to development on the OSD: The OSD 1.0 Developer Home: this is the one stop shop for development information, documentation and guides for OSD developers. It's also home of the Guide to Hacking the OSD, our main developer guide.

Ingenient Technologies is the BSP (board support package) vendor, which includes modifications to a Linux 2.6 kernel and proprietary binary codecs that leverage the DSP core of the processor. For more generic information on the platform, see DM320 Platform development.

[edit] OSD 2.0

Work has also begun on the next generation OSD 2.0 Platform. This is high def capable version based on TI's Davinci Chipset and using VLC as the playback engine. Internal samples are just being released, with a developer kit coming approximately End of June.

[edit] The Resources

The Neuros online community provides many resources:

[edit] Neuros Development Wiki

• Neuros Development Wiki
  • Currently being written by crweb (Tom) these pages are for those wanting to dig deeper into both development and programming for libraries and applications on the Neuros Platforms.

[edit] IRC

• #neuros on Freenode
  • 24/7 live discussion within the Neuros community
  • Accessible directly from your web browser: Web IRC Client
  • Meetings are often scheduled, see OdNT for announcements
  • IRC logs, accurate nearly to the hour: http://open.neurosaudio.com/irclogs/

[edit] Mailing List (Google Groups)

• Neuros@googlegroups.com - General Development
  • To subscribe via e-mail, send to Neuros-susbcribe@googlegroups.com
  • Online at Google Groups: Neuros
• neuros-patches@googlegroups.com - Public(Read-Only) Patch & Review
  • To subscribe via e-mail, send to neuros-patches-susbcribe@googlegroups.com
  • Online at Google Groups: Neuros-Patches

[edit] Web

• OdNT: http://open.neurostechnology.com/
  • Web portal for open-source Neuros development
  • Blogs, links to IRC discussions

[edit] Bug Tracking

• Neuros Bugzilla: http://bugzilla.neurostechnology.com/
  • Tracks all bugs and enhancement requests (including hardware and software)
  • It's very important that everyone feel free to contribute bugs and comments. This allows Neuros to have accurate feedback and for you to participate in design decisions.
  • Only requests in this database get systematically reviewed with each new design planning period; all official changes happen after reviewing the information in this database

[edit] Source Control

• Subversion (SVN): svn://svn.neurostechnology.com/svn/ (also http://svn.neurostechnology.com/svn/)
  • Main place for Neuros code, including the custom kernel, drivers and UI code
  • WebSVN access: http://svn.neurostechnology.com/
  • Repositories include:
    • Nano-X: Microwindows for the Neuros (akin to an X server); see README
    • neuros-bsp: Board support package by Ingenient Technologies (modified U-Boot and Linux kernel, also binary drivers for the DSP core); see README
    • Neuros-Cooler: Shared Neuros libraries and widget/GUI framework; see README
  • The following requirements/steps will get you write permission to the repository:
    • Willingness to follow the very minimum requirements each time before you commit code to trunk: send out patch and make sure it is reviewed by the maintainer first.
    • Send your request to project maintainer (mgao at neuros dot us).

• External developer repository: https://svn.neurostechnology.com/
  • Separate repository used by external developers/hackers
  • Among other things, contains derobert's build script, 00_Build.sh.

[edit] The People

A handful of developers are Neuros employees, but many are simply passionate hackers (in the "experienced programmer" sense). Neuros is generally promoting an open and transparent atmosphere, so everyone is welcome and encouraged to contribute in their way.

If you need to contact an administrator, look for:

• crweb, nerochiaro (this wiki, OdNT, mailing list)
• derobert, DeepB, srobertson, Xorlev (all of the above plus svn accounts and general servers administration)

Open source contributors and advanced users:

• Mattj: lpkg and lua
• greyback: Forums and support
• ChadV: Forums and support
• koen: OSD2 OpenEmbedded

Neuros also has an internal team spread across the world.

• The Western Team includes:
  • nerochiaro (Ugo Ribioni) (Developer, Manager): The Over Seer, Patch Review, all things team & hardware related
  • crweb (Tom Bruno) (Developer, Manager): GUI, networking, userspace, patch review
  • turran (Jorge Jorge Luis Zapata Muga) (Developer, Manager): Kernel space, drivers, hardware, patch review
  • John Olson (Designer): Graphics and Casing Designer

• The Xiamen Team includes:
  • Corlin: Team Manager and Head of Schedules
  • Terry Qiu (Developer): uboot & updater
  • Frank Xue (Developer): build system & gerneral development
  • John Wu (Developer): kernel space, uboot, ubl
  • Welsy Xie (Developer): GUI, userspace
  • Peter Qiu: Network administrator, release builder

• The Taiwan Team includes:
  • Jimmy Chen: Developer (hardware drivers, HDMI)

Archive:

[edit] FAQ

Please see Developer FAQ.

This wiki is user updated and the information here cannot be considered official Neuros communication