Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

lalaki

Members
  • Joined

  • Last visited

Reputation Activity

  1. Like
    @lalakii is In Armbian for chips, allwinner uses only a branch with kernel.org . There is no special branch for a separate chip.
     
    There is a series of patches that were taken from different places or made by different users and added to the series file.
    The binary files that you kindly provided are useless for the build system.
    Links to download from Google drive are also not useful.
    All you need is to apply a series of patches to the corresponding kernel branch as a "git am" command.
    Then make your comments on top with explanations and an indication of the author. Then extract these last commits using a script.
    cp armbian/build/tools/mk_format_patch $USER/bin; chmod +x $USER/bin mkdir -p $USER/tmpwork/patches.armbian cd /path/to/linux-stable mk_format_patch . HEAD~7..HEAD $USER/tmpwork/patches.armbian I think that you have guessed where they need to be placed, make a commit in the build system itself and make a pull request.
  2. Like
    hi, just like to join this discussion in a 'development' sense
    it seemed there are some works in the head Linux v6.5-rc1
    https://groups.google.com/g/linux-sunxi/c/p64EM9m9inY
    https://linux-sunxi.org/Xunlong_Orange_Pi_Zero3
    https://linux-sunxi.org/Linux_mainlining_effort
     
    they seemed to be continued works on H616 mainlining efforts, but that those are working on H618 e.g. Orange Pi zero 3 etc
    it could be good to look at the head revisions e.g. v6.5 when we 'backport' codes into e.g. v6.1.31 that is used with armbian.
    that could save a lot of rework if at some point we (armbian) decide to move on and use a new kernel e.g. v6.5
    and accordingly, i read a post that say things like the wifi drivers as different vendors tried to implement their own drivers, it creates a 'problem' for the mainlining efforts to attempt to reconcile 2 different versions of the 'same driver'.  Hence, it may be good to look at head revisions e.g. v6.5 while 'porting' them back into v6.1.31. it would likely allow us to have 1 version of drivers e.g. from mainline that possibly works on different boards using the same wifi chips etc.
     
     
  3. Like
    Armbian does not provide images for this board nor does it support it (yet). The OS you are using comes from a 3rd party. So I suggest to ask for support where you got the image from.
  4. Like
    Usually provide a difference file.
    Please, if you want to share the results of your work, make a set of patches as the output of the "git format-patch" command.
    Or a more time-consuming but faster way to make a pull request directly to the project on github.
  5. Like
    After a few days of trying to get rid of these annoyances by modifying the kernel source code as well as the device tree, I've finally gotten rid of them, and now there are only a few inconsequential warnings

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.