search

jddiener / I2C-eTPU

This project is an I2C eTPU driver that supports all the major features of the standard. A single master or slave instance uses 4 eTPU channels/pins.
https://www.ashware.com/i2c-driver
Eclipse Public License 2.0
1 stars 1 forks source link

Please consider dual licence #1

Open AndrewD opened 4 weeks ago

AndrewD commented 4 weeks ago

Would you consider licensing this project with a second, more common, licence: eg BSD or Apache.

I would like to avoid the complication of getting a new licence approved for our use for just one library.

We actively contribute to several projects, this request is purely to minimise non-technical overhead.

This appears to be a nice clean library and I'd prefer to use it instead of creating another solution.

AndrewD commented 4 weeks ago

I just noticed most of your other repo are using the MIT license which would also be ok for our usage.

jddiener commented 4 weeks ago

I dual-licensed it. If you end up having feedback on the software, it is appreciated.

-john

From: AndrewD @.> Sent: Friday, September 27, 2024 4:01 PM To: jddiener/I2C-eTPU @.> Cc: Subscribed @.***> Subject: Re: [jddiener/I2C-eTPU] Please consider dual licence (Issue #1)

I just noticed most of your other repo are using the MIT license which would also be ok for our usage.

— Reply to this email directly, view it on GitHub https://github.com/jddiener/I2C-eTPU/issues/1#issuecomment-2380159914 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSHTLNIAF76EGECIDLRGMTZYXIQBAVCNFSM6AAAAABO76CH2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBQGE2TSOJRGQ . You are receiving this because you are subscribed to this thread. https://github.com/notifications/beacon/ALSHTLNRIIPZEVXDQCRF76LZYXIQBA5CNFSM6AAAAABO76CH2GWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUN3ZN2U.gif Message ID: @. @.> >

AndrewD commented 4 weeks ago

Thanks for doing this, it's greatly appreciated. I'll let you know how we go.

One observation was that it requires 4 TPU channels; I can understand this requirement with some early eTPU implementations like 5554, but I suspect it's feasible to do bidirectional data on a single channel with more recent devices. Is this something you have looked into?

jddiener commented 4 weeks ago

Agree, it would be interesting to generate a 2-channel version. This was discussed some 2-3 years ago but didn’t happen. The original versions of this code were written quite a long time ago, back when MPC55xx support was more important. It’s been quite a while since I’ve gotten into the details of the code, but there is a good chance it is a relatively straight-forward enhancement. I ran a couple of the sim tests and didn’t spot any resource usage issues that would for sure force larger design changes. But it was a cursory look.

-john

From: AndrewD @.> Sent: Friday, September 27, 2024 8:10 PM To: jddiener/I2C-eTPU @.> Cc: jddiener @.>; Comment @.> Subject: Re: [jddiener/I2C-eTPU] Please consider dual licence (Issue #1)

Thanks for doing this, it's greatly appreciated. I'll let you know how we go.

One observation was that it requires 4 TPU channels; I can understand this requirement with some early eTPU implementations like 5554, but I suspect it's feasible to do bidirectional data on a single channel with more recent devices. Is this something you have looked into?

— Reply to this email directly, view it on GitHub https://github.com/jddiener/I2C-eTPU/issues/1#issuecomment-2380355072 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSHTLJY35DBAFWAZDDZYQ3ZYYFY5AVCNFSM6AAAAABO76CH2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBQGM2TKMBXGI . You are receiving this because you commented.Message ID: @.***>