Jump to content

lsmod

Members
  • Posts

    34
  • Joined

  • Last visited

Everything posted by lsmod

  1. O.K. Thank you ! This is really much information for me with a lot solutions for my problem - Thank you all! So first i try out the simple sysfs, because it seems that i don't need a new kernel. Then i will have a look on ArmbianIO, because this looks like an comfortable way to access ports - if it works for the H5. The direct C-Code for the PWM can be helpful. It is also possible to mix C and Perl if needed. I will report when i have tested it and when it is successfull. But this can take some time ...
  2. My first choice for small projects is to program in perl. It's near C, but i don't need to compile and it is fast and stable. The python library could be something to use with PerlXS Hmm - at this time i don't understand the sense of this definitions ... Now i find the links for Armbian IO - this could be interesting for others: https://github.com/bitbank2/ArmbianIO
  3. No - normally it has not to be fast. Just switching some things on and off or read slow signals. But PWM output could be interesting. When Bit hacking through sysfs is a universal working solution - this will be sufficient - thanks. I just want to be sure that it is possible when i use Armbian for the H5 board PC 2. Python is not my language, but i will have a look at Armbian IO ...
  4. I did not do many things so far with WiringPi, and i did it on an original Pi B+ in the past. But now i want to do again some working with the OrangePi and so i want to use the ports too. What are alternatives for a simply access of the ports of an H3 and H5 in shell and perl? When there is a working alternative everything is fine and i don't have to do nasty things with the kernel ... I want to use I2C for a DS3231 hardware clock.
  5. Yes - i did have the same idea, but without no effect. I am only a C novice and there seems to be more checks or i just failed ...
  6. O.K. This is a really simple approach. But i know it will take many dependencies and time to get it working. I suppose BRANCH="next" is the "testing" and not "stable"? Is there no lazy way for me to take a kernel package from http://beta.armbian.com/ for a quick test ? I searched but could not find an appropriate package ... It seems that the "p1" makes a certain sense. So i think it is better and easier to patch the WiringPi instead of the kernel.
  7. Besides - here are the CPU types that are checked in OrangePi.c of WiringPi: I see a difference to your patch with sun50iw1p1 ? /* * Probe OrangePi Platform. */ int isOrangePi(void) { FILE *cpuFd; char line [120]; char *d; #ifdef CONFIG_ORANGEPI_2G_IOT /* Support: OrangePi 2G-IOT and OrangePi i96 */ char *OrangePi_string = "rda8810"; #elif CONFIG_ORANGEPI_PC2 /* Support: OrangePi PC2 */ char *OrangePi_string = "sun50iw2"; #elif CONFIG_ORANGEPI_A64 /* Support: OrangePi Win/Win plus */ char *OrangePi_string = "sun50iw1"; #elif CONFIG_ORANGEPI_H3 /* Support: OrangePi Win/Win plus */ char *OrangePi_string = "sun8iw7"; #elif CONFIG_ORANGEPI_ZERO /* Support: OrangePi zero */ char *OrangePi_string = "sun8iw7"; #else /* Non-support */ char *OrangePi_string = "none"; #endif if ((cpuFd = fopen("/proc/cpuinfo", "r")) == NULL) piBoardRevOops ("Unable to open /proc/cpuinfo") ; while (fgets(line, 120, cpuFd) != NULL) { if (strncmp(line, "Hardware", 8) == 0) break; } fclose(cpuFd); if (strncmp(line, "Hardware", 8) != 0) piBoardRevOops("No \"Hardware\" line");
  8. Thank you for the info Igor. I already expected such an answer. Is there an easy way to recompile the kernel with this patch ? I never have done such things for an ARM kernel ... Or how can i use the kernel of the nightly build in the stable distribution ? It would be nice if such things like WiringPi would be part of armbian. Why are I2C tools included, but no tools regarding the IO-ports ?
  9. Hello together, i opened a ticket here https://github.com/armbian/build/issues/1085 Why "cat /proc/cpuinfo" does not tell anything about the CPU type?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines