[Espressobin support development efforts]

Another quick question: 

Is there anyway that we can use the second UART port in P9 connector? I know something need to change to generate new dtb file to enable that. Is there any easy way to download or generate this file? 

 

Thanks a lot. 

 

p.s. digging on the internet and found this: 

https://patchwork.kernel.org/patch/9988925/

 

The reason why UART is not enabled: "... because both headers are dedicated to expose general purpose pins and remapping some of them to use the second UART would break existing users."

 

However, after checking the GPIO mapping, I found PIN 24&26 on P9 header are used for UART only, not possibly messing around with other GPIO pins. It should be opened at the beginning.

 

Can we have a dts file with this option on?  Maybe I have to learn how to compile the dts file myself. 

 

 

[Espressobin support development efforts]

19 hours ago, tkaiser said:

 

Hopefully fixed with https://github.com/armbian/build/commit/dc9ad0e1e5993cbe92bbbe25417a419fa1fc1123

Thanks a lot! 

[Espressobin support development efforts]

On 8/31/2018 at 7:32 AM, tkaiser said:

 

Which doesn't change much wrt the name of Linux kernel modules that provide SMB3 client functionality  

 

Speaking about Linux naming conventions: 'mount_smb' is the deprecated variant of 'mount_cifs' that should be used today. And this most probably originated from the history of SMB/CIFS support in Linux. Two decades ago SMB could've been best described as a pile of rotten protocols that are pretty much useless since Microsoft's implementations differed in almost any detail. Compared to that CIFS was an advancement (read through Linux manual pages -- many of this historical stuff still there). SMB2 and SMB3 have nothing in common with the SMB we know from 2 decades ago. Robust protocols with lots of cool features and specifications worth the name.

 

Anyway: CONFIG_CIFS is not set on just 5 kernel variants (by accident) so @sunxishan please send a PR with them enabled as module.

Hi tkaiser thanks for your reply. I would love to submit the PR however when I checked the config file it labelled as auto-generated file. I am not familiar with this building procedure how I generate this config file. 

 

[Espressobin support development efforts]

I am curious why not the cifs support built in release.

 

linux-mvebu64-default.config: CONFIG_CIFS=m

linux-mvebu64-dev.config:# CONFIG_CIFS is not set

linux-mvebu64-next.config:# CONFIG_CIFS is not set

 

should we have this basic module at lease CONFIG_CIFS=m as in default config?