This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://firstname.lastname@example.org/.246tnt at gmail.com 246tnt at gmail.com
> what if there is already a scheduled item? in this case i must schedule > the frequency change item before any other item. also the frame number > of frequency change may be more than 255 frames ahead. Feel free to extend the scheduler to fit your needs. > my suggestion: because hopping sequence is a function of time, the > starting time should also be included in this function (rfch.c). The only function in rfch.c returns the parameter for a given time. It does _NOT_ and should _NOT_ make any change to the parameter itself. That's left up to the caller because we need to call that function several time. If you want to introduce some call that configure the channel and make changes and stuff, put it into another function and make sure it's called when required. Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100907/e7220de6/attachment.htm>