Investigate C-Sky architecture
an invention by a_faerber
Updated over 5 years ago. 1 hackers ♥️. 1 follower.

The youngest architecture addition to the mainline Linux kernel was C-Sky (arch/csky/).

I have a GX6605S board booting a downstream 4.9 kernel. It uses a proprietary GxLoader bootloader (similarities with U-Boot exist but no sources...) with uImage and gx6605s.dtb files in a FAT partition on USB stick.

I prepared a csky-elf GCC cross-toolchain and would like to try building and booting a mainline kernel on that board. This will involve writing a mainline-compatible .dts for this board that, if successful, I could contribute upstream.

Besides learning about this architecture and any commonalities and differences, I am curious whether I can use the 3 accessible GPIOs on the board for connecting any radio transceivers for testing my LoRa, FSK, etc. kernel network drivers. Too little for bit-banging SPI, I guess, and seemingly no pin-muxing to UART. Maybe some I²C sensor though?

Looking for hackers with the skills:

csky kernel

This project is part of:

Hack Week 18

Activity

  • over 5 years ago: lyan liked this project.
  • over 5 years ago: a_faerber added keyword "csky" to this project.
  • over 5 years ago: a_faerber added keyword "kernel" to this project.
  • over 5 years ago: a_faerber started this project.
  • over 5 years ago: a_faerber originated this project.


    • Comments

    • a_faerber
      over 5 years ago by a_faerber | Reply

      It was confirmed today that upstream GCC is still lacking support for ck610. So my sub-project of packaging a csky-elf abiv1 cross-compiler is dead for now.

    • a_faerber
      over 5 years ago by a_faerber | Reply

      Yesterday compiled and booted mainline and linux-next kernels (up to an error executing the init process), sending out a patch for the Device Tree I derived.

    Similar Projects

    Improve various phones kernel mainline support (Qualcomm, Exynos, MediaTek) by pvorel

    Similar to previous hackweeks ( https://hackweek.opensuse.org/projects/improve-qualcomm-soc-msm8994-slash-msm8992-kernel-mainline-support, https://hackweek.opensuse.org/projects/test-mainline-kernel-on-an-older-qualcomm-soc-msm89xx-explore-mainline-kernel-qualcomm-mainlining) try to improve kernel mainline support of various phones.

    Kill DMA and DMA32 memory zones by ptesarik

    Description

    Provide a better allocator for DMA-capable buffers, making the DMA and DMA32 zones obsolete.

    Goals

    Make a PoC kernel which can boot a x86 VM and a Raspberry Pi (because early RPi4 boards have some of the weirdest DMA constraints).

    Resources

    • LPC2024 talk:
    • video:

    Modernize ocfs2 by goldwynr

    Ocfs2 has gone into a stage of neglect and disrepair. Modernize the code to generate enough interest.

    Goals: * Change the mount sequence to use fscontext * Move from using bufferhead to bio/folios * Use iomap * Run it through xfstests

    Modularization and Modernization of cifs.ko for Enhanced SMB Protocol Support by hcarvalho

    Creator:
    Enzo Matsumiya ematsumiya@suse.de @ SUSE Samba team
    Members:
    Henrique Carvalho henrique.carvalho@suse.com @ SUSE Samba team

    Description

    Split cifs.ko in 2 separate modules; one for SMB 1.0 and 2.0.x, and another for SMB 2.1, 3.0, and 3.1.1.

    Goals

    Primary

    Start phasing out/deprecation of older SMB versions

    Secondary

    • Clean up of the code (with focus on the newer versions)
    • Update cifs-utils
    • Update documentation
    • Improve backport workflow (see below)

    Technical details

    Ideas for the implementation.

    • fs/smb/client/{old,new}.c to generate the respective modules
      • Maybe don't create separate folders? (re-evaluate as things progresses!)
    • Remove server->{ops,vals} if possible
    • Clean up fs_context.* -- merge duplicate options into one, handle them in userspace utils
    • Reduce code in smb2pdu.c -- tons of functions with very similar init/setup -> send/recv -> handle/free flow
    • Restructure multichannel
      • Treat initial connection as "channel 0" regardless of multichannel enabled/negotiated status, proceed with extra channels accordingly
      • Extra channel just point to "channel 0" as the primary server, no need to allocate an extra TCPServerInfo for each one
    • Authentication mechanisms
      • Modernize algorithms (references: himmelblau, IAKERB/Local KDC, SCRAM, oauth2 (Azure), etc.

    Officially Become a Kernel Hacker! by m.crivellari

    Description

    My studies as well my spare time are dedicated to the Linux Kernel. Currently I'm focusing on interrupts on x86_64, but my interests are not restricted to one specific topic, for now.

    I also "played" a little bit with kernel modules (ie lantern, a toy packet analyzer) and I've added a new syscall in order read from a task A, the memory of a task B.

    Maybe this will be a good chance to...

    Goals

    • create my first kernel patch

    Resources

    Achivements