Staars

Members
  • Content Count

    39
  • Joined

  • Last visited

About Staars

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Staars

    Rock64 Revision 3.0

    Does the SD card appear later in the boot process, when you boot from eMMC?
  2. Staars

    Proof of concept - Realtek 1295

    This is only for sake of booting it somehow, but at least: _ _ _ | | __ _| | _____ / | | | / _` | |/ / _ \ | | | |__| (_| | < __/ | | |_____\__,_|_|\_\___| |_| Welcome to ARMBIAN 5.77 user-built Debian GNU/Linux 9 (stretch) 4.19.16-rtd1295 System load: 2.81 1.25 0.47 Up time: 2 min Memory usage: 5 % of 1932MB IP: CPU temp: 42°C Usage of /: 15% of 7.1G This is useful for nothing at the moment (no usb, no net, no straightforward installation method), but I am not yet in the state to give up. It is a buggy mess at the moment and again I have not uploaded all stuff to my repo. To reach this pseudo-success, I had to boot with kernel 4.9.y, then let armbian resize the initial image (which does not work with 4.19.y for whatever reason) and then write the 4.19.-kernel and the DTB to the SD-card. So it is a bit of a click-bait
  3. Staars

    Proof of concept - Realtek 1295

    Hmmm, moving slowly foward: After digging deeper and deeper, I think that I could get some things to work, but to be honest: I had hoped, that this would be easier. I did not upload all the new things yet, so this is not repeatable at the moment. Hopefully there is more to come.
  4. Staars

    Proof of concept - Realtek 1295

    So, crash improvement from 0 to about 4 seconds with 4.19.: ... little by little ..
  5. Staars

    Proof of concept - Realtek 1295

    First Thanx for the hint with the non-soldering method. This is way easier! The new 4.19-images crashes immediately, but this is not totally unexpected. I will look into it. BTW, are you able to enter the mode, where we can write the SPI-rom? Like so: http://forum.zidoo.tv/index.php?threads/how-to-flash-zidoo-x9s-unit.2959/page-13 ATM, I assume that there is no SPI on the Lake-Box.
  6. Staars

    Proof of concept - Realtek 1295

    [ o.k. ] Writing U-boot bootloader [ /dev/loop0 ] [ o.k. ] Done building [ /home/vagrant/armbian/output/images/Armbian_5.76_Lake1_Debian_stretch_dev_4.19.16.img ] Some updates: 1. Now I have a kernel tree based on stable 4.19.16 which should include most of the realtek specific files from the vendor kernel and compiles. There was a lot of guesswork and I am by no means a kernel developer. 2. After some updates to the build files it is now possible to create a disc image for default and dev. It might be possible to build a vanilla mainline kernel now, but a new kernel config file would be needed. 3. My new Lake-TV-Box has finally arrived (but I am too lazy to solder the UART connection right now).
  7. Staars

    Proof of concept - Realtek 1295

    a small teaser: dpkg-deb: building package 'linux-source-4.19.16-dev-rtd1295' in '/home/vagrant/armbian/.tmp/linux-source-dev-rtd1295_5.76_all.deb'. [ o.k. ] Kernel build done [ @host ] [ o.k. ] Target directory [ /home/vagrant/armbian/output/debs/ ] [ o.k. ] File name [ linux-image-dev-rtd1295_5.76_arm64.deb ] [ o.k. ] Runtime [ 4 min ] This can definitely NOT work atm, because some parts (i.e. DTS) are missing, but it is moving in the right direction.
  8. Staars

    Proof of concept - Realtek 1295

    I have nothing to show yet and I just decided, to refactor my efforts again. To give a rough overview about my (unprofessional) approach so far: I have taken a standard 4.19.16 kernel and the "obvious" realtek files from the bsp-realtek-kernel. Then came the iterative compile->error-message->fix cycle, which really showed some progress and I could work out all the API changes so far (untested of course!). The nasty thing is, that there are various "realtek patches" all over the place and not only in the soc specific driver code. So you got to see lots of #ifdef CONFIG_RTK_blablabla in generic kernel code parts. The other problem is, that the tiny amount of RTD1295 code that is already in the kernel does interfere sometimes and does not include the concept of different realtek socs (119x, 129x, 139x, 16xx) of the family. There is no one to blame for (not realtek and not the kernel code contributor), but it does not make things easier. My initial idea (before I had a real overview about the code) was to integrate the bsp-realtek-1295-stuff into the already existing kernel-code (which basically is 1295, but with a generic name), but meanwhile I think, that this was a bad idea. What I will try now is to strip the realtek-mainline-parts and introduce the generic realtek platform with the different socs in my kernel fork. In a best-case-scenario this might work somehow in the end, but at best it should show no or small regression compared to the current 4.9.159-bsp-version. Mainlining this will be impossible (for me) but with a bit (extreme amounts) of luck it could be easier to patch newer kernels in the future. I am convinced, that it should be quite easy for realtek to do this or at least to change their code base to a more modular/driver-based model and I'm even more convinced that it would make their job easier in the future (watch for instance at about minute 38). But don't be surprised, if this does not work at all !!
  9. Staars

    Proof of concept - Realtek 1295

    Thanx for reporting. But to dig deeper, I really need the actual hardware I am making some progress on the 4.19.-front. There are lots of API changes in the kernel between 4.9 and 4.19, but I hope to get it done.
  10. Staars

    Proof of concept - Realtek 1295

    That looks good. Is ethernet working for you? BTW, my attempts to create a patched kernel tree (4.19) were not exactly successful and I will have to gain some knowledge before I seriously can expect some results. At least it does not get boring
  11. Staars

    Proof of concept - Realtek 1295

    Curiosity is a very good reason (it is basically the only reason for this whole thread)! You are right, the dtb and kernel function in the script is hard coded atm. To be honest, I only tested my SATA drive as boot device (did not spend very much time with it). Can you access it with fdisk? I will use my spare time in the next days to play with the 4.19.-kernel, but do not expect fast results here.
  12. Staars

    Proof of concept - Realtek 1295

    It is funny, but just hours before your post I started my first steps to work on a 4.19-kernel. The general problem with vendor kernels is, that it might be possible to port it to a newer mainline kernel, but with every new kernel version the whole thing restarts again. Without upstreaming to mainline nothing is really won in the long term. The current situation with 4.9.-LTS-kernel with support until 2023 is not extremely bad. Do you need a special feature of kernel>4.19? To boot from sata I only had to „clone“ the sd card partition with dd and change the bootargs. Your log shows, that there is no working DTB loaded. I will my use „box-less“ time to extend the configs in my repo to support 4.19 and report here, when I think that it is ready for a test (or when I have a box again myself).
  13. Staars

    Proof of concept - Realtek 1295

    Cool! Can you test Wifi, because I had to finalize the patches after I bricked my box. For me the easiest way to do this over UART was: nmcli device wifi connect SSID-Name password wireless-password
  14. Staars

    Proof of concept - Realtek 1295

    Short update on Wifi/BT: I switched to the combi-88xx-drivers, which were added to armbian recently. To enable BT I had to create a patch, which turns off the firmware upload in /drivers/bluetooth/btrtl.c. The behavior should be quite 'vanilla' now and I could scan the BT-(LE)-devices of my neighborhood without problems.
  15. Staars

    Proof of concept - Realtek 1295

    Yes, we can do it that way and I will try to „maintain“ it. Indeed it might me a good idea to show, why this platform is far away from getting official support. Even though I invested a bit of work, I can not really recommend this box with productivity in mind. At the moment it is a very interesting toy. It is a pity that realteks strategy does not really involve the linux/open source world, but they may have their reasons. Anyway, I‘m curious to see how far we can get here. Probably I can not post anything new in the next few weeks, because I have to wait for my new box. I really bricked the first one (and I will explain my stupid error in an extra post).