Hi all,
I suspect Erik is right - ALi may not have good or up-to-date
documentation. Therefore, perhaps we should think about asking for any
source that they may have - for the Windows driver, any other (e.g.
embedded system) drivers and even any simple test programs they have
internally.
If they do have datasheets, even if the datasheets are not 'sufficient'
they will be a giant leap forward from what we are currently working
against (basically reverse engineering and guesswork). If they want a bit
more detail on which registers we would like information on then I would
suggest:
- Clock generation control
- Frame control and timing
- I2C
But obviously the more the better.
Regards,
Richard
To
"Franck Bourdonnec"
<[EMAIL PROTECTED]>
"Erik Andrén" cc
<[EMAIL PROTECTED] [EMAIL PROTECTED]
om> e.net
Subject
Sent by: Re: [M560x-driver-devel] Contact
m560x-driver-devel-b with Ali Corp.
[EMAIL PROTECTED] Classification
orge.net
05/06/2008 20:55
Hi,
2008/6/5 Franck Bourdonnec <[EMAIL PROTECTED]>:
Le Thursday 05 June 2008 17:13:31 Accord Tsai, vous avez écrit :
> They had not been terribly enthusiastic about it, but I have received
> an email reply from the marketing manager.
>
> He explains that "due to company policy we are unable to provide
> datasheets. Furthermore, the datasheets may not be sufficient for your
> needs. Perhaps you could tell me what kind of data you need, and we'll
> see if there's anything I can do."
>
> I've replied about the hardware capabilities and register mapping.
>
it's fairly simple: the doc they gave to allow someone using the
microsoft DDK
to write a driver for windows for their chip. No more, no less.
There is no thousand of doc. It is available or it is not. ALI won't
rewrite
a subset of doc for a chip(alim5603c) specifically for 'another system'
(linux).
The existing doc was enougth for window, the same is sufficient for
linux!
Linux is not a martian OS, it is a system running on standart PC
architecture.
Remember them that simple fact ;-)
There might be no doc or the doc might be of such a low quality that they
don't want to spend any engineering resources to fix it up for release.
Sometimes the ASIC engineer designing the chip sits next to the driver
writer and the driver is writting using informal communication (i. e by
asking questions without any formal specs).
This might be embarrasing for the company to admit and instead they try to
cover everything by blaming on "company policy".
This, of course, is pure speculation on my side.
Regards,
Erik
Franck
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
M560x-driver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
M560x-driver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel
<<inline: graycol.gif>>
<<inline: pic18054.gif>>
<<inline: ecblank.gif>>
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php
_______________________________________________ M560x-driver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel
