I've raised an issue on google code although not sure if it is properly tracked.
As a consequence I've tried first to get optiboot from here...
Who can replace a bootloader in the repository and accept a library code change?
Or rather - what's the correct process to do it (as it seems issues tab is used just to track internal code changes)?
"Properly tracked"? What does that mean?
I believe Tom Carpenter is the original author of the version included in the Tiny Core...https://github.com/TCWORLD/ATTinyCorehttps://github.com/TCWORLD/ATTinyCore/tree/master/tiny
The Issues list is my (partial) work list. Creating an entry there is a good start.Discussing changes here is a good choice.
Any suggestion to my second question? So far I didn't find any better way rather than creating variants folder, moving default build_options to standard variant and adding that standard variant to all non-optiboot boards, and creating custom variant for optiboot one.
How do I submit changes btw? Series of patches (aka lklm) or pull request (aka github)?
Oh, so I'm working on non-up-to-date repo, that explains the things.
Where's that brand new core2 please?
...if there's any maillist for that.
Is the tiny85 optiboot theoretically compatible with the "main" optiboot that is over at http://code.google.com/p/optiboot/ ?I haven't paid any attention to the soft uart version there (for "luminet", supposedly), it's quite a bit bigger, and I have no idea whether it is working at all...
• Included a variation of Tiny Tuner with the upload image so the very first time the processor booted the internal oscillator could be tuned.
... it's quite a bit bigger, and I have no idea whether it is working at all...
Please enter a valid email to subscribe
We need to confirm your email address.
To complete the subscription, please click the link in the
email we just sent you.
Thank you for subscribing!
via Egeo 16