Skip site navigation (1)Skip section navigation (2)


2020/freebsd-arm/20201011.freebsd-arm

Messages: 95, new messages first
Last update: Mon Feb 13 14:14:44 2023

home | archive sorted by: subject | author | date | reverse date
  1. Oct 10 Klaus Cucinauomo           Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
  2. Oct 10 Mark Millard               Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
  3. Oct 10 Mark Millard               RPi4B: modern firmware vs. Device tree loaded to 0x4000 (size 0xbe0c) [fails] vs. to 0x1f0000 (size 0xbd90) [works]?
  4. Oct 10 Mark Millard               Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
  5. Oct 10 Mark Millard               Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
  6. Oct 10 Klaus Cucinauomo           Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
  7. Oct 10 Mark Millard               Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
  8. Oct 10 Mark Millard               Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
  9. Oct 10 Klaus Cucinauomo           Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
 10. Oct  9 Klaus Cucinauomo           Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
 11. Oct  9 Mark Millard               Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
 12. Oct  9 Mark Millard               Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
 13. Oct  9 Klaus Cucinauomo           Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
 14. Oct  9 Klaus Cucinauomo           Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
 15. Oct  9 Mark Millard               Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
 16. Oct  9 Klaus Cucinauomo           Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
 17. Oct  9 Mark Millard               Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
 18. Oct  9 Klaus Cucinauomo           Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
 19. Oct  9 Klaus Cucinauomo           Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
 20. Oct  9 Kyle Evans                 Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)


21. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 22. Oct 9 bob prohaska Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 23. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 24. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 25. Oct 9 Warner Losh Re: ARMv7 without VFP 26. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 27. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 28. Oct 9 bob prohaska Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 29. Oct 9 Kyle Evans Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 30. Oct 9 bob prohaska Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 31. Oct 8 Marcin Wojtas ARMv7 without VFP 32. Oct 8 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 33. Oct 8 Kyle Evans Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 34. Oct 8 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 35. Oct 8 John-Mark Gurney RFC: allow first boot config from msdos partition 36. Oct 8 Kyle Evans Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 37. Oct 8 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 38. Oct 8 Kyle Evans Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 39. Oct 8 Kyle Evans Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 40. Oct 8 Klaus Cucinauomo Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
41. Oct 8 Sleep Walker Re: FreeBSD-13.0-CURRENT on Helios64 Kobol NAS 42. Oct 8 Mark Millard RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 43. Oct 7 Emmanuel Vadot Re: BBB boot failure between r366365 and r366386 44. Oct 7 Oskar Holmlund Re: BBB boot failure between r366365 and r366386 45. Oct 7 KIRIYAMA Kazuhiko Where is the rk3399-pinebook-pro.dtb ? 46. Oct 7 Daniel Braniss Re: nanopi/allwinner i2c not working. 47. Oct 7 Daniel Braniss Re: nanopi/allwinner i2c not working. 48. Oct 7 Andriy Gapon Re: nanopi/allwinner i2c not working. 49. Oct 7 Andriy Gapon Re: nanopi/allwinner i2c not working. 50. Oct 7 Daniel Braniss Re: nanopi/allwinner i2c not working. 51. Oct 7 Andriy Gapon Re: nanopi/allwinner i2c not working. 52. Oct 7 Daniel Braniss Re: nanopi/allwinner i2c not working. 53. Oct 7 Warner Losh Re: generic q on freebsd 54. Oct 7 Mark Millard Re: generic q on freebsd 55. Oct 7 Mark Millard Adding a "-1" into https://reviews.freebsd.org/D25219 's code looks to make uefi/ACPI handle USB3 SSD reliably 56. Oct 7 Daniel Braniss Re: nanopi/allwinner i2c not working. 57. Oct 7 Kamal Prasad Re: generic q on freebsd 58. Oct 7 Kamal Prasad Re: generic q on freebsd 59. Oct 7 Andriy Gapon Re: nanopi/allwinner i2c not working. 60. Oct 7 Mark Millard Re: A basis for a possible update to the pcie based xhci support? It survived huge-file duplicate-then-diff testing so far.
61. Oct 7 Mark Millard A basis for a possible update to the pcie based xhci support? It survived huge-file duplicate-then-diff testing so far. 62. Oct 7 Klaus Cucinauomo Re: RPI4 U-Boot 2020.10-rc5 please test xhci feature 63. Oct 7 Ed Maste Re: BBB boot failure between r366365 and r366386 64. Oct 6 Mark Millard Re: rpi4 FreeBSD vs. ubuntu u-boot fdt print / memereserve difference (lack of reserve in FreeBSD context), 0x3b400000 vs. DMA_HIGH_LIMIT bein 65. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 66. Oct 6 Ed Maste Re: BBB boot failure between r366365 and r366386 67. Oct 6 Warner Losh Re: generic q on freebsd 68. Oct 6 Kamal R. Prasad generic q on freebsd 69. Oct 6 Andriy Gapon Re: nanopi/allwinner i2c not working. 70. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 71. Oct 6 Andriy Gapon Re: nanopi/allwinner i2c not working. 72. Oct 6 Mark Johnston Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3 73. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 74. Oct 6 Andriy Gapon Re: nanopi/allwinner i2c not working. 75. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 76. Oct 6 Andriy Gapon Re: nanopi/allwinner i2c not working. 77. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 78. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 79. Oct 6 Emmanuel Vadot Re: nanopi/allwinner i2c not working. 80. Oct 6 Andriy Gapon Re: nanopi/allwinner i2c not working.
81. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 82. Oct 6 bob prohaska panic: non-current pmap 0xffffa00020eab8f0 on Rpi3 83. Oct 5 Ed Maste Re: BBB boot failure between r366365 and r366386 84. Oct 5 Daniel Braniss Re: nanopi/allwinner i2c not working. 85. Oct 5 Andriy Gapon Re: nanopi/allwinner i2c not working. 86. Oct 5 Ed Maste BBB boot failure between r366365 and r366386 87. Oct 5 Marcin Wojtas Re: HEADS UP: NXP LS1046A SoC support in the tree 88. Oct 5 Daniel Braniss nanopi/allwinner i2c not working. 89. Oct 5 Klaus Cucinauomo RPI4 U-Boot 2020.10-rc5 please test xhci feature 90. Oct 4 Mark Millard Re: rpi4 FreeBSD vs. ubuntu u-boot fdt print / memereserve difference (lack of reserve in FreeBSD context), 0x3b400000 vs. DMA_HIGH_LIMIT bein 91. Oct 4 Robert Crowston Re: lspci XHCI "Memory at" for RPi4 (u-boot based context): FreeBSD vs. ubuntu vs. "Memory behind bridge" addresses 92. Oct 4 Robert Crowston Re: RPi4B 3 GiByte pcie limitation: The following change survived my huge-file duplicate-and-diff tests so far 93. Oct 4 Mark Millard Re: RPi4B u-boot based booting and hw.cpufreq.voltage_core and dev.cpu.0.freq use: able to use 2000 MHz 94. Oct 4 Mark Millard Re: rpi4 FreeBSD vs. ubuntu u-boot fdt print / memereserve difference (lack of reserve in FreeBSD context), 0x3b400000 vs. DMA_HIGH_LIMIT bein 95. Oct 4 Mark Millard Re: lspci XHCI "Memory at" for RPi4 (u-boot based context): FreeBSD vs. ubuntu vs. "Memory behind bridge" addresses


home | archive sorted by: subject | author | date | reverse date