2010/3/29 Rob Hamerling <[email protected]> > > Hi Seb, > > On 29/03/10 07:47 am, Sebastien Lelong wrote: > > [RobH] > > To help finding an answer to my question I've added some statistical >> information to the FindJANSEL wiki: a list of PICs for the different >> cases. If you need more or better info (I'm thinking of listing the >> PICs in groups using the same dataset), shouldn't be to difficult. >> Suggestions are welcome. >> >> >> This is interesting, users may refer to this list, at least to know when >> ADC pins are dependent or not. Could you split this information and put >> in an another page, so they won't get flooded by too much data ? I'll >> then add a link in headers. >> > > You mean a separate wiki with only the bottom part of the current FindANSEL > wiki? Could be done, I think.
I can do it of course, but it may be generated. Let me know. > Did you see the latest wiki with the group-sorted list? Is that suitable > for you and the users? Not sure. Is it content beginning from "Number of PICs listed..." to the end ? This is what I see as a dedicated wiki page for users. > > To answer your question, if a new PIC is added: >> >> - if ADC pins are dependent (case 1, controlled by PCFG bits), ADC >> libs must be re-generated, PIC must be added to pinmap.py and pcfg.py >> (see http://code.google.com/p/jallib/wiki/UpdatingPinmap) >> > > Update of pinmap.py will probably be done by me when a new device file > appears. But I systematically forget to update pcfg.py, sorry. > I can take care of pcfg.py to share the burden... > > So there is no warning signal to update ADC libs. That was one of my doubts > about ADC libs being up to date. AFAIK, they are now up-to-date. Cheers, Seb -- 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.
