00:00 <Hawk777> You could override the handler in your own config file.

00:01 <Hawk777> You could either copy and paste the original handler into your overriding handler and customize what’s needed, or potentially figure out the Tcl way to read the existing handler into a variable, then attach your own handler that runs the original one and then changes the adapter speed afterward.

00:01 <c4017w__> yeah, I was wondering if the handlers are chainable

00:01 <c4017w__> that would be one option

00:01 <Hawk777> There’s no built-in support for chaining AFAIK, and sadly most of the shipped config files don’t use named functions for them.

00:13 <c4017w__> Is there any point submitting a patch for a flash driver and algorithm that's hardcoded for one particular chip? I likely won't have time to implement any changes that come from the review

04:01 <olerem> c4017w__: if you have no time to respond on review, then if will be nice to not submit the patches. reviewing takes a lot of time and spendig this time without and response is bad

06:21 <PaulFertser> c4017w__: I think it's better to submit but state no intention to accept review in the commit message.

06:22 <PaulFertser> c4017w__: because that patch will appear in Internet search engines and someone else might directly benefit or even pick it up and re-submit with upstreaming intentions.

06:22 <olerem> good point

16:09 <c4017w__> I was thinking that if I submit it, at least someone else can find and use it. Just don't want to add clutter. I'll clean it up a bit and submit it

16:49 <PaulFertser> c4017w__: thank you