On 2/24/08, PcgScrapAddy <[EMAIL PROTECTED]> wrote: > > This is one of our primary goals in terms of making a GPU for high-end > > embedded systems. > > > Excellent. I have experience with the eCos RTOS and am yearning to dive > into uCLinux as well so I'd like to be kept in the loop when addressing > the embedded space if possible.
We also would like to support the broadest possible set of platforms. And in addition, we need well-documented development and lots of MIT-licensed code that would allow any embedded system builder to make our chip work with their system. (Not to mention community support on the list.) > > for some high-priority loose end ... > > Is there a bulletin or some other notification method of what is in dire > need? What bug tracker do you use? Online project management software? I > see you use Subversion which is fantastic, I switched my company to it > so no learning curve there. This might be a good place to start. http://wiki.opengraphics.org/tiki-index.php?page=VGACodeSprint > As a side note: I do have 8 years of IT experience with informal > training on the business side so feel free to leverage that experience > as you see fit. If you are looking to build your company completely on > OSS then I have probably already investigated all the software you would > ever need. How about funding and loans? :) > > > We're also trying to move forward on a hardware IDE that will help us > > with designing hardware pipelines. > > > What base framework are you using? Eclipse w/ CDT? Or something else. I > am pretty ignorant when it comes to hardware so please bare with me. I started with NetBeans. I haven't used Eclipse more than looking at it once or twice, but NetBeans looks less busy to me. > > People just latch on to something interesting, ... > > Tim, > > For some background info I'd like to send you a PDF of my resume to your > direct email account, is that ok? Sure, if you like. > That may help you determine what you > have to work with and where to allocate/ask me to help out. For at least the next few weeks, I'm swamped. I won't be able to do a very good job of _assigning_ you something (indeed, that's something I tend not to do), but I can guide you towards areas that need work, and others on the list should have suggestions as well. > While I am > partial to doing Linux drivers I also know that sometimes something else > may need attention to move forward. I'm no guru by any stretch so > helping you get some working Linux drivers may be a good place for me to > become intimate with your product and go from there but you may see > something different. Your call, it is your project. A good thing for anyone on this project to do is to get a passing familiarity with Verilog (there are tutorials pointed to from www.opengraphics.org), HDL simulation (we mostly use Icarus Verilog), and waveform viewers (for instance GTKwave). Obviously, we need software development, but there are some hardware things in the critical path, and being familiar with the hardware will make the software easier to write. Thanks again. -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
