2020/freebsd-arm/20201011.freebsd-arm
Messages: 95, sorted by subject
|
Last page update: Sat Jan 3 13:06:26 UTC 2026
|
|
home | up | archive | sorted by: subject - author - date - reverse date
1. 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. 2. 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. 3. Oct 7 Mark Millard Adding a "-1" into https://reviews.freebsd.org/D25219 's code looks to make uefi/ACPI handle USB3 SSD reliably 4. Oct 8 Marcin Wojtas ARMv7 without VFP 5. Oct 9 Warner Losh Re: ARMv7 without VFP 6. Oct 5 Ed Maste BBB boot failure between r366365 and r366386 7. Oct 5 Ed Maste Re: BBB boot failure between r366365 and r366386 8. Oct 6 Ed Maste Re: BBB boot failure between r366365 and r366386 9. Oct 7 Ed Maste Re: BBB boot failure between r366365 and r366386 10. Oct 7 Oskar Holmlund Re: BBB boot failure between r366365 and r366386 11. Oct 7 Emmanuel Vadot Re: BBB boot failure between r366365 and r366386 12. Oct 8 Sleep Walker Re: FreeBSD-13.0-CURRENT on Helios64 Kobol NAS 13. Oct 6 Kamal R. Prasad generic q on freebsd 14. Oct 6 Warner Losh Re: generic q on freebsd 15. Oct 7 Kamal Prasad Re: generic q on freebsd 16. Oct 7 Kamal Prasad Re: generic q on freebsd 17. Oct 7 Mark Millard Re: generic q on freebsd 18. Oct 7 Warner Losh Re: generic q on freebsd 19. Oct 5 Marcin Wojtas Re: HEADS UP: NXP LS1046A SoC support in the tree 20. Oct 4 Mark Millard Re: lspci XHCI "Memory at" for RPi4 (u-boot based context): FreeBSD vs. ubuntu vs. "Memory behind bridge" addresses
21. Oct 4 Robert Crowston Re: lspci XHCI "Memory at" for RPi4 (u-boot based context): FreeBSD vs. ubuntu vs. "Memory behind bridge" addresses 22. Oct 5 Daniel Braniss nanopi/allwinner i2c not working. 23. Oct 5 Andriy Gapon Re: nanopi/allwinner i2c not working. 24. Oct 5 Daniel Braniss Re: nanopi/allwinner i2c not working. 25. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 26. Oct 6 Andriy Gapon Re: nanopi/allwinner i2c not working. 27. Oct 6 Emmanuel Vadot Re: nanopi/allwinner i2c not working. 28. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 29. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 30. Oct 6 Andriy Gapon Re: nanopi/allwinner i2c not working. 31. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 32. Oct 6 Andriy Gapon Re: nanopi/allwinner i2c not working. 33. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 34. Oct 6 Andriy Gapon Re: nanopi/allwinner i2c not working. 35. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 36. Oct 6 Andriy Gapon Re: nanopi/allwinner i2c not working. 37. Oct 6 Daniel Braniss Re: nanopi/allwinner i2c not working. 38. Oct 7 Andriy Gapon Re: nanopi/allwinner i2c not working. 39. Oct 7 Daniel Braniss Re: nanopi/allwinner i2c not working. 40. Oct 7 Daniel Braniss Re: nanopi/allwinner i2c not working.
41. Oct 7 Andriy Gapon Re: nanopi/allwinner i2c not working. 42. Oct 7 Daniel Braniss Re: nanopi/allwinner i2c not working. 43. Oct 7 Andriy Gapon Re: nanopi/allwinner i2c not working. 44. Oct 7 Andriy Gapon Re: nanopi/allwinner i2c not working. 45. Oct 7 Daniel Braniss Re: nanopi/allwinner i2c not working. 46. Oct 7 Daniel Braniss Re: nanopi/allwinner i2c not working. 47. Oct 6 bob prohaska panic: non-current pmap 0xffffa00020eab8f0 on Rpi3 48. Oct 6 Mark Johnston Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3 49. Oct 8 John-Mark Gurney RFC: allow first boot config from msdos partition 50. Oct 5 Klaus Cucinauomo RPI4 U-Boot 2020.10-rc5 please test xhci feature 51. Oct 7 Klaus Cucinauomo Re: RPI4 U-Boot 2020.10-rc5 please test xhci feature 52. 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 53. 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 54. 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 55. Oct 4 Robert Crowston Re: RPi4B 3 GiByte pcie limitation: The following change survived my huge-file duplicate-and-diff tests so far 56. 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 57. Oct 8 Mark Millard RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 58. Oct 8 Klaus Cucinauomo Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 59. Oct 8 Kyle Evans Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 60. Oct 8 Kyle Evans Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
61. Oct 8 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 62. Oct 8 Kyle Evans Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 63. Oct 8 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 64. Oct 8 Kyle Evans Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 65. Oct 8 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 66. Oct 9 bob prohaska Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 67. Oct 9 Kyle Evans Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 68. Oct 9 bob prohaska Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 69. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 70. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 71. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 72. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 73. Oct 9 bob prohaska Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 74. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 75. Oct 9 Kyle Evans Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 76. Oct 9 Klaus Cucinauomo Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 77. Oct 9 Klaus Cucinauomo Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 78. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 79. Oct 9 Klaus Cucinauomo Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 80. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
81. Oct 9 Klaus Cucinauomo Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 82. Oct 9 Klaus Cucinauomo Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 83. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 84. Oct 9 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 85. Oct 9 Klaus Cucinauomo Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 86. Oct 10 Klaus Cucinauomo Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 87. Oct 10 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 88. Oct 10 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 89. Oct 10 Klaus Cucinauomo Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 90. Oct 10 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 91. Oct 10 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 92. Oct 10 Mark Millard Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 93. Oct 10 Klaus Cucinauomo Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) 94. Oct 10 Mark Millard RPi4B: modern firmware vs. Device tree loaded to 0x4000 (size 0xbe0c) [fails] vs. to 0x1f0000 (size 0xbd90) [works]? 95. Oct 7 KIRIYAMA Kazuhiko Where is the rk3399-pinebook-pro.dtb ?
home | up | archive | sorted by: subject - author - date - reverse date