#avr Logs

Mar 26 2019

12:26 AM gsi__ is now known as gsi_
12:44 AM day_ is now known as day
09:01 AM ville: i was looking at http://www.nongnu.org/avr-libc/user-manual/group__avr__interrupts.html and there doesn't appear to be "atmega32u4" specifically in any rows of the "applicable for device". there is "atmega32". does this cover the u4?
09:04 AM ville: http://www.nongnu.org/avr-libc/user-manual/ lists atmega32u4 as a supported device
09:13 AM timemage: ville, different animal. 32u4 is supported, i imagine 32 is also. what are you looking for?
09:23 AM ville: timemage: i am using the atmega32u4, and i was looking at what interrupts are supported on it. am i to gather none?
09:24 AM timemage: ville, heh, nah. if they're missing from the lists i'm not sure why that would be. but it's prefectly well supported. they're all supported. even if the didn't have names in the support files (they do), you'd be able to use the generic numbered vector names.
09:24 AM ville: alright
09:26 AM timemage: ville, if you look in your avr-libc directories, you can find /include/avr/iom32u4.h
09:27 AM timemage: ville, alternately: avr-gcc -mmcu=atmega32u4 -E -dM -x c - <<< '#include <avr/io.h>' | grep _vect
09:31 AM ville: thanks. i've poked around those files. was kind of hoping to get by by reading documentation rather than poking around source files directly
09:31 AM ville: but it seems like lot of the things are not documented in the http://www.nongnu.org/avr-libc/user-manual/modules.html or at least the search doesn't seem to show them
09:33 AM timemage: ville, the documentation is doxygen generated, so it's in the source. assuming they didn't fail to put the doxygen stuff in the file, you could run the program yourself and it would produce the same file as the site with whatever the current comments are.
09:34 AM timemage: ville, usually that sort of thing would be done with \group or whatever.
09:34 AM vmt: you're being naive /at best/ thinking commie documentation is complete in any way, shape or form.
09:36 AM vmt: did i say commie? i meant foss. gotta run, prayer. our rms who art though in mom's basement
09:36 AM vmt: prayer time*
09:36 AM vmt: oh ffs. dear rms who art thou in mom's basement.
09:37 AM ville: plenty of foss software projects have good documentation
09:37 AM vmt: sure. the kind of borderline trivial ones
09:42 AM timemage: ville, looks like that part of the documentation isn't auto-generated, even though it's marked with the group. there's a file vectortable.dox that just has a static table in it.
09:43 AM skz81: Proprietary software is NO WARRANTY of a good quality document. https://pics.me.me/this-cat-spushing-a-watermelon-outofa-lake-your-argument-is-37905094.png
09:50 AM vmt: at no point did i mention the word proprietary. you're a moron and keep your watermelon
04:23 PM [1]MrMobius is now known as MrMobius
05:27 PM davor_ is now known as davor
06:48 PM rue_mohr: uh
06:48 PM rue_mohr: whats with the unfriendly attitude?
06:54 PM vmt: nothing really, just tired of commie github-hippies always making excuses for shitty and lacking foss-documentation by saying "hurrdurr there's shitty proprietary docs too"
06:56 PM rue_mohr: dude, all software has suckass for documentation
06:57 PM rue_mohr: thats why everyone is better off writing everything themselvs
06:57 PM rue_mohr: the idea of supplying your code to anyone else, so that they can apply it to whatever the hell their trying to do is insane
06:58 PM rue_mohr: code only works properly for the author
06:58 PM rue_mohr: most open source projects can ONLY be compiled by the developers, casue they ahve such an insane dependency tree that the developers machine is the only one that can build it