On Wed, Apr 21, 2021 at 9:04 AM Tim <t...@jti.uk.com.invalid>> wrote:
>> I am in need of a driver for an FUSB301 USB C Controller/PD device. I see >> there are drivers for the FUSB301 and FUSB303 but not the FUSB302. >> >> >> >> Before I have a stab at porting the outline code I already have for this >> device, and finishing it off to become a "proper" NuttX driver (and >> potentially making it my first ever contribution), I thought I would ask >> first to see if there is one lurking somewhere and I just missed it? >> >> >> >> Also, a question from an old-school SW developer and (therefore) GitHub & >> Apache/incubator newbie: if I simply want to ask advice do I still email >> dev@nuttx.apache.org <mailto:dev@nuttx.apache.org>> or should it be to a >> different email address? I see some emails I get from the reflector (if >> that's what it's called) have an unsubscribe option, whereas others do not >> and it seems to relate to how the question/comment has originated? Be kind >> to me :) >Hello Tim, >I can't answer your first question about the FUSB30x driver(s), but >regarding your second question: Yes, dev@nuttx.apache.org is the correct >place to discuss NuttX-related subjects, including development (as the name >dev@ implies) and user questions. But if you ever need to report security >issues, those should not be publicly disclosed until we release a fix, so >please report such issues to priv...@nuttx.apache.org instead. >We're always glad to have new contributors! Feel free to open a Pull >Request at GitHub at any time. See this helpful link: >https://nuttx.apache.org/docs/latest/contributing/index.html >In particular, the page Making Changes Using Git (second from the top) will >help walk you through the process of dealing with GitHub etc. >Cheers, >Nathan Thanks Nathan. I only found this reply on the mail archives - I never had a notification of a reply for some reason :( I have been reading up on how to use Github - and the link you provided - and am poised to start doing this "properly": I have found a number of errors in SamA5 related files and rather than raise them as issues it makes more sense for me to fix them I think. These easy fixes will get me used to the process and I will then feel more confident in submitting new drivers - it looks like I'll be creating at least 4 that may just be of use to someone else (FUSB302 USB C Controller, ACT8945 Power Management , LP5036 multi-channel RGB LED driver, ADPS-9901 ambient light/proximity sensor.).
