> Perhaps if there's a group effort put towards obtaining the timings > for 320M > from Koping it would help? Afterall what are they going to lose by > telling > us the timing for their > product, it should be in the specs anyways. Yet the gain I see is that > we'd > put to use their old recycled displays and give them another life... The datasheet for the Kopin 320M is available on their website, and includes timing diagrams along with other information. (Or at least it did, I haven't rechecked in the last week or so :-) > I dont think I'd like to drive it via parallel or USB port (besides as > you > said not having enough bandwidth), I was thinking a VGA signal which > should > give it a decent quality and edge over the composite that's currently > being > in use with the Motorola driver chip. If you're wanting to drive the display by streaming information over a USB 1.1 link (i.e. you pump out each and every pixel for each and every frame) then you are pushing against the upper limit of USB throughput if you use 1-bit monochrome graphics (although I suppose you could reduce the frame rate). Off course, you could always use a framebuffer, then the USB could send information whenever it needs to update the screen, rather than continuously (the display would read from the framebuffer, rather than expecting to be fed by the USB stream). I have some VHDL code referenced from my weblog that I hope produces all the correct *digital* signals for the Kopin 320M display. I got a little disallusioned when after mentioning it here previously I had so little feedback (although that have been one or two new visitors in the last few days). My display is intended purely as a 1-bit monochrome display - I'm hoping that this will make the display nice and crisp, and I don't see any advantages *for*me* of having grey scale or colour images super-imposed over the real world. Once the display side of my VHDL code has been proven (no doubt changes will be necessary), it shouldn't be too hard to adapt it to a greater number of greyscales. > With so many displays in the circulation today (heck I even got a pack > of 42 > myself) I feel it should be a viable solution/idea to try and connect > them > with something else than Motorola driver because eventually Motorola > will > say NO to sample requests once they figure out what we are doing here. > I > mean there must be hundreds of these displays now in posession of > various > individuals around the world, surely that number should warrant for > some > collective effort :) I agree one hundred percent - these chips aren't cheap, and Motorola will wise up eventually - we need a longer term solution. Other people are going to come on the scene in the future and they need to have something to build upon. I also have an aversion to converting from the digital domain, to analogue, and back again (i.e. computer -> video-signal -> converter -> display) - all that extra hardware consumes power. Regarding using a processor - I think you'd be hard pushed to do this on a processor without some sort of additional hardware. You won't find you have time to execute many instructions between setting out the correct control signals for each clock. Thanks, Duncan. (I would write more, but my dog wants out - bye for now). -- Subscription/unsubscription/info requests: send e-mail with subject of "subscribe", "unsubscribe", or "info" toWear-Hard Mailing List Archive (searchable): http://wearables.blu.org Please, *PLEASE* don't subscribe through a forward/expander/false domain
From Wear-Hard Mailing list Archive (WH)
Maintained by R. Paul McCarty
Archive created with babymail