Sebastien Lelong wrote:
> I understand that even if organizing search a work may costs time (telling
> who's doing what), you can't be the only one who has to dig every datasheet
> to find the secret formula. You have to share the burden :)
But I can update my scripts/lists directly, other people would have to
make a list and I would have to update my stuff with those lists. So I
think it is more efficient to do it all by myself (see also below).
> I also understand your point about reputation, but... it already happened
> that someone has found a bug, or an non-working device file or library.
> Reactivity was then clearly high, and this is also about reputation I think.
> IMO, we'd better spend time on what users are using or are likely to use,
> not what they will hardly use. And in the meantime, provides more external
> libraries, protocols, improve peripheral libs (like the ADC one...).
Agreed! So I'll do a last check and wait for a beep...
>>From what you say, I understand you want to let things as they are (running
> a beep-system). Or... do you want to read these 35 datasheets alone ? If so,
> please take the time to give some of them to me, even if you may waste some
> explaining to me where to look, I'm sure I'll learn many things :)
Well, it's only about ADCONx registers. I have a list with PICs that
have an ADCONx register (the FindAnalog.wiki) and I can skip PICs
without one, so less than 35 datasheets to go!
Regards, Rob.
--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---
