Contributor meeting notes 19-Jan-21
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call - Current time is the best across US, Europe, India. But not any good for East Asia - Simon might send out survey - Send invitation to maintainer group - DONE [Simon] New sequence numbers [Heinrich] Online docs - https://u-boot.readthedocs.io/ - Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
Regards, Simon
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://u-boot.readthedocs.io/
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
- Can we use e.g. jitsi meet next time , or even better IRC ?
- Does this have to be every two weeks ? Why two weeks ?
Hi Marek,
On Tue, 19 Jan 2021 at 13:27, Marek Vasut marex@denx.de wrote:
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://u-boot.readthedocs.io/
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
- Can we use e.g. jitsi meet next time , or even better IRC ?
We already IRC a lot. This is partly about getting to know each other.
What is the benefit of jitsi? I believe I am permitted to use it,
- Does this have to be every two weeks ? Why two weeks ?
Do you mean it should be more frequent or less?
Regards, Simon
Hi Simon,
I think I should add my $0.02 here.
We already IRC a lot. This is partly about getting to know each other. What is the benefit of jitsi? I believe I am permitted to use it,
Jitsi is a free and lightweight solution: it's free/open-source and there's also a free public server (more than one, strictly speaking: 1 official cluster + several 3rd party public servers). It doesn't require installing anything (just a web browser), it doesn't require registration (although anyone can use self-hosted instance and configure access control lists as they wish), it doesn't limit meeting duration. As far as I know, it's also not blocked in China (while most commercial solutions are blocked for years, google products are among them, although they're popular and VPN helps sometimes), this is beneficial too. I wanted to suggest Jitsi during previous discussion as I'm using it for several years and it does its job pretty well (just one job, though: no built-in file sharing, no fancy chat formatting, just audio+video meetings and plain-text chat).
It's quite sad for me to see so many people prefering that proprietary Z**m thing and struggling with its limitations last year while there are mostly better free products that are enough for most use-cases but just didn't get enough attention.
Cheers, Alex
On 1/20/21 12:44 AM, Simon Glass wrote:
Hi Marek,
Hi,
[...]
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://u-boot.readthedocs.io/
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
- Can we use e.g. jitsi meet next time , or even better IRC ?
We already IRC a lot. This is partly about getting to know each other.
What is the benefit of jitsi? I believe I am permitted to use it,
It seems Alex covered this part already pretty well.
- Does this have to be every two weeks ? Why two weeks ?
Do you mean it should be more frequent or less?
I think we should agree on what is best in a discussion.
In my opinion, once a month is enough.
Hi Simon, Tom,
On 20.01.21 16:05, Marek Vasut wrote:
On 1/20/21 12:44 AM, Simon Glass wrote:
Hi Marek,
Hi,
[...]
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://u-boot.readthedocs.io/
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
- Can we use e.g. jitsi meet next time , or even better IRC ?
We already IRC a lot. This is partly about getting to know each other.
What is the benefit of jitsi? I believe I am permitted to use it,
It seems Alex covered this part already pretty well.
Indeed - DENX has already set a server with Jitsi for videoconference, and we are actively using to communicate with customers. DENX can offer to host the meeting for U-Boot (Wolfgang has already agreed) - we have all advantages reported by Marek and Alex. Simon, Tom: is it this suitable for you ? We can switch to Jitsi since next meeting.
Best regards, Stefano
Hi Stefano,
Thank you for the offer!
What are the advantages of hosting the meeting on a private server?
Regards, Simon
On Thu, 21 Jan 2021 at 01:14, Stefano Babic sbabic@denx.de wrote:
Hi Simon, Tom,
On 20.01.21 16:05, Marek Vasut wrote:
On 1/20/21 12:44 AM, Simon Glass wrote:
Hi Marek,
Hi,
[...]
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://u-boot.readthedocs.io/
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
- Can we use e.g. jitsi meet next time , or even better IRC ?
We already IRC a lot. This is partly about getting to know each other.
What is the benefit of jitsi? I believe I am permitted to use it,
It seems Alex covered this part already pretty well.
Indeed - DENX has already set a server with Jitsi for videoconference, and we are actively using to communicate with customers. DENX can offer to host the meeting for U-Boot (Wolfgang has already agreed) - we have all advantages reported by Marek and Alex. Simon, Tom: is it this suitable for you ? We can switch to Jitsi since next meeting.
Best regards, Stefano
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de =====================================================================
Hi Simon,
On 27.01.21 22:31, Simon Glass wrote:
Hi Stefano,
Thank you for the offer!
What are the advantages of hosting the meeting on a private server?
No, I do not see any special advantage - I will just be happy (as Marek) if we can nuse a FOSS project as Jitsi for communication. IMHO it is ok to use the public server provided by jitsi.
Regards, Stefano
Hi Stefano.
On Thu, 28 Jan 2021 at 02:24, Stefano Babic sbabic@denx.de wrote:
Hi Simon,
On 27.01.21 22:31, Simon Glass wrote:
Hi Stefano,
Thank you for the offer!
What are the advantages of hosting the meeting on a private server?
No, I do not see any special advantage - I will just be happy (as Marek) if we can nuse a FOSS project as Jitsi for communication. IMHO it is ok to use the public server provided by jitsi.
OK well we tried a jitsi call last week and it seemed to work fine.
Regards, Simon
Hi,
I have updated the invitation to include a jitsi call. We can try that and fall back to Google Meet if something goes wrong.
I have also added a call in Asia timezone. Please see the notes[1] for details.
Regards, Simon
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
On Wed, 20 Jan 2021 at 08:05, Marek Vasut marex@denx.de wrote:
On 1/20/21 12:44 AM, Simon Glass wrote:
Hi Marek,
Hi,
[...]
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://u-boot.readthedocs.io/
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
- Can we use e.g. jitsi meet next time , or even better IRC ?
We already IRC a lot. This is partly about getting to know each other.
What is the benefit of jitsi? I believe I am permitted to use it,
It seems Alex covered this part already pretty well.
- Does this have to be every two weeks ? Why two weeks ?
Do you mean it should be more frequent or less?
I think we should agree on what is best in a discussion.
In my opinion, once a month is enough.
On Wed, Jan 20, 2021 at 2:54 AM Simon Glass sjg@chromium.org wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
Goot to see we have online docs configured to display the U-Boot documentation. Previously I suggested we have denx.de host this, but looks we never went that way.
- Accept a merge request only with docs included?
I am not sure what this means. Is the https://u-boot.readthedocs.io/ setup to build daily?
Next meeting Tuesday 2 Feb.
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
Regards, Bin
On 20.01.21 02:55, Bin Meng wrote:
On Wed, Jan 20, 2021 at 2:54 AM Simon Glass sjg@chromium.org wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
Goot to see we have online docs configured to display the U-Boot documentation. Previously I suggested we have denx.de host this, but looks we never went that way.
- Accept a merge request only with docs included?
I am not sure what this means. Is the https://u-boot.readthedocs.io/ setup to build daily?
Building u-boot.readthedocs.io ==============================
Building https://u-boot.readthedocs.io/ is controlled by file .readthedocs.yml.
Whenever Tom pushes to https://github.com/u-boot/u-boot.git branch master the documentation is built. Building for a tag must be triggered manually on page https://readthedocs.org/projects/u-boot/.
Currently Tom and I have administrator privileges for the project on readthedocs.io.
Requiring documentation =======================
Many changes that we do are worth being documented:
* new or changed commands * new boards * API changes
The idea is that the maintainers should push the contributors to provide documentation for relevant changes and possibly reject patch sets with missing documentation.
Best regards
Heinrich
On 1/21/21 11:41 AM, Heinrich Schuchardt wrote:
On 20.01.21 02:55, Bin Meng wrote:
On Wed, Jan 20, 2021 at 2:54 AM Simon Glass sjg@chromium.org wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
Goot to see we have online docs configured to display the U-Boot documentation. Previously I suggested we have denx.de host this, but looks we never went that way.
- Accept a merge request only with docs included?
I am not sure what this means. Is the https://u-boot.readthedocs.io/ setup to build daily?
Building u-boot.readthedocs.io
Building https://u-boot.readthedocs.io/ is controlled by file .readthedocs.yml.
Whenever Tom pushes to https://github.com/u-boot/u-boot.git branch master the documentation is built. Building for a tag must be triggered manually on page https://readthedocs.org/projects/u-boot/.
Currently Tom and I have administrator privileges for the project on readthedocs.io.
Requiring documentation
Many changes that we do are worth being documented:
- new or changed commands
- new boards
- API changes
The idea is that the maintainers should push the contributors to provide documentation for relevant changes and possibly reject patch sets with missing documentation.
Please extend tools to catch this. I use patman which calls checkpatch. When maintainers get reminders situation will improve. Not sure if make sense to add any rule to gitlab CI to fail but that's also one way to go.
Thanks, Michal
Hi,
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers
I can't see any issue with it on zynqmp platform. There is only issue with i2c which was there for quite a long time that i2c mux is considered as chip on the subbus as is visible below.
i2c 0 [ + ] i2c_cdns | |-- i2c@ff030000 gpio 1 [ + ] pca953x | | |-- gpio@20 i2c_mux 0 [ + ] pca954x | | `-- i2c-mux@74 i2c 1 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@0 i2c_eeprom 0 [ + ] i2c_eeprom | | | `-- eeprom@54 i2c 2 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@1 i2c_generi 0 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 1 [ + ] i2c_generic_chip_drv | | | |-- generic_6c i2c_generi 2 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 3 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@2 i2c_generi 3 [ + ] i2c_generic_chip_drv | | | |-- generic_13 i2c_generi 4 [ + ] i2c_generic_chip_drv | | | |-- generic_14 i2c_generi 5 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 6 [ + ] i2c_generic_chip_drv | | | |-- generic_43 i2c_generi 7 [ + ] i2c_generic_chip_drv | | | |-- generic_44 i2c_generi 8 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 4 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@3 i2c_generi 9 [ + ] i2c_generic_chip_drv | | | |-- generic_0 i2c_generi 10 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 11 [ + ] i2c_generic_chip_drv | | | |-- generic_40 i2c_generi 12 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 5 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@5 i2c_generi 13 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 14 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 6 [ + ] i2c_mux_bus_drv | | `-- i2c@ff030000->i2c-mux@74->i2c@7 i2c_generi 15 [ + ] i2c_generic_chip_drv | | |-- generic_19 i2c_generi 16 [ + ] i2c_generic_chip_drv | | |-- generic_20 i2c_generi 17 [ + ] i2c_generic_chip_drv | | |-- generic_36 i2c_generi 18 [ + ] i2c_generic_chip_drv | | |-- generic_37 i2c_generi 19 [ + ] i2c_generic_chip_drv | | |-- generic_51 i2c_generi 20 [ + ] i2c_generic_chip_drv | | `-- generic_74
Thanks, Michal
Hi Michal,
On Wed, 20 Jan 2021 at 00:46, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers
I can't see any issue with it on zynqmp platform. There is only issue with i2c which was there for quite a long time that i2c mux is considered as chip on the subbus as is visible below.
Do you mean the naming of the device, or something else? What happens if you type 'i2c bus'?
i2c 0 [ + ] i2c_cdns | |-- i2c@ff030000 gpio 1 [ + ] pca953x | | |-- gpio@20 i2c_mux 0 [ + ] pca954x | | `-- i2c-mux@74 i2c 1 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@0 i2c_eeprom 0 [ + ] i2c_eeprom | | | `-- eeprom@54 i2c 2 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@1 i2c_generi 0 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 1 [ + ] i2c_generic_chip_drv | | | |-- generic_6c i2c_generi 2 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 3 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@2 i2c_generi 3 [ + ] i2c_generic_chip_drv | | | |-- generic_13 i2c_generi 4 [ + ] i2c_generic_chip_drv | | | |-- generic_14 i2c_generi 5 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 6 [ + ] i2c_generic_chip_drv | | | |-- generic_43 i2c_generi 7 [ + ] i2c_generic_chip_drv | | | |-- generic_44 i2c_generi 8 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 4 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@3 i2c_generi 9 [ + ] i2c_generic_chip_drv | | | |-- generic_0 i2c_generi 10 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 11 [ + ] i2c_generic_chip_drv | | | |-- generic_40 i2c_generi 12 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 5 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@5 i2c_generi 13 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 14 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 6 [ + ] i2c_mux_bus_drv | | `-- i2c@ff030000->i2c-mux@74->i2c@7 i2c_generi 15 [ + ] i2c_generic_chip_drv | | |-- generic_19 i2c_generi 16 [ + ] i2c_generic_chip_drv | | |-- generic_20 i2c_generi 17 [ + ] i2c_generic_chip_drv | | |-- generic_36 i2c_generi 18 [ + ] i2c_generic_chip_drv | | |-- generic_37 i2c_generi 19 [ + ] i2c_generic_chip_drv | | |-- generic_51 i2c_generi 20 [ + ] i2c_generic_chip_drv | | `-- generic_74
Regards, Simon
On 1/20/21 4:44 PM, Simon Glass wrote:
Hi Michal,
On Wed, 20 Jan 2021 at 00:46, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers
I can't see any issue with it on zynqmp platform. There is only issue with i2c which was there for quite a long time that i2c mux is considered as chip on the subbus as is visible below.
Do you mean the naming of the device, or something else? What happens if you type 'i2c bus'?
If look at log below. mux is at address 74 which is i2c_mux_bus_drv and when you run i2c dev <any i2c mux channel> and run i2c probe i2c mux itself is assigned to to i2c_generic_chip_drv. Below you see it multiple times as generic_74 with ID 2/8/12/14/20. All of them are just targeting i2c mux.
Thanks, Michal
i2c 0 [ + ] i2c_cdns | |-- i2c@ff030000 gpio 1 [ + ] pca953x | | |-- gpio@20 i2c_mux 0 [ + ] pca954x | | `-- i2c-mux@74 i2c 1 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@0 i2c_eeprom 0 [ + ] i2c_eeprom | | | `-- eeprom@54 i2c 2 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@1 i2c_generi 0 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 1 [ + ] i2c_generic_chip_drv | | | |-- generic_6c i2c_generi 2 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 3 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@2 i2c_generi 3 [ + ] i2c_generic_chip_drv | | | |-- generic_13 i2c_generi 4 [ + ] i2c_generic_chip_drv | | | |-- generic_14 i2c_generi 5 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 6 [ + ] i2c_generic_chip_drv | | | |-- generic_43 i2c_generi 7 [ + ] i2c_generic_chip_drv | | | |-- generic_44 i2c_generi 8 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 4 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@3 i2c_generi 9 [ + ] i2c_generic_chip_drv | | | |-- generic_0 i2c_generi 10 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 11 [ + ] i2c_generic_chip_drv | | | |-- generic_40 i2c_generi 12 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 5 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@5 i2c_generi 13 [ + ] i2c_generic_chip_drv | | | |-- generic_20 i2c_generi 14 [ + ] i2c_generic_chip_drv | | | `-- generic_74 i2c 6 [ + ] i2c_mux_bus_drv | | `-- i2c@ff030000->i2c-mux@74->i2c@7 i2c_generi 15 [ + ] i2c_generic_chip_drv | | |-- generic_19 i2c_generi 16 [ + ] i2c_generic_chip_drv | | |-- generic_20 i2c_generi 17 [ + ] i2c_generic_chip_drv | | |-- generic_36 i2c_generi 18 [ + ] i2c_generic_chip_drv | | |-- generic_37 i2c_generi 19 [ + ] i2c_generic_chip_drv | | |-- generic_51 i2c_generi 20 [ + ] i2c_generic_chip_drv | | `-- generic_74
Regards, Simon
Hi Michal,
On Wed, 20 Jan 2021 at 08:50, Michal Simek michal.simek@xilinx.com wrote:
On 1/20/21 4:44 PM, Simon Glass wrote:
Hi Michal,
On Wed, 20 Jan 2021 at 00:46, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers
I can't see any issue with it on zynqmp platform. There is only issue with i2c which was there for quite a long time that i2c mux is considered as chip on the subbus as is visible below.
Do you mean the naming of the device, or something else? What happens if you type 'i2c bus'?
If look at log below. mux is at address 74 which is i2c_mux_bus_drv and when you run i2c dev <any i2c mux channel> and run i2c probe i2c mux itself is assigned to to i2c_generic_chip_drv. Below you see it multiple times as generic_74 with ID 2/8/12/14/20. All of them are just targeting i2c mux.
That's strange. I wonder if it is failing to find it and creating multiple copies?
+Heiko Schocher too
Regards, Simon
On 1/21/21 5:11 AM, Simon Glass wrote:
Hi Michal,
On Wed, 20 Jan 2021 at 08:50, Michal Simek michal.simek@xilinx.com wrote:
On 1/20/21 4:44 PM, Simon Glass wrote:
Hi Michal,
On Wed, 20 Jan 2021 at 00:46, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers
I can't see any issue with it on zynqmp platform. There is only issue with i2c which was there for quite a long time that i2c mux is considered as chip on the subbus as is visible below.
Do you mean the naming of the device, or something else? What happens if you type 'i2c bus'?
If look at log below. mux is at address 74 which is i2c_mux_bus_drv and when you run i2c dev <any i2c mux channel> and run i2c probe i2c mux itself is assigned to to i2c_generic_chip_drv. Below you see it multiple times as generic_74 with ID 2/8/12/14/20. All of them are just targeting i2c mux.
That's strange. I wonder if it is failing to find it and creating multiple copies?
+Heiko Schocher too
I have never had a time to dig into this. But I expect that i2c mux enables one channel and i2c probe just correct detects all devices on bus before mux and also the whole subbus. But we are missing to check for every detected device if that address is listed already.
Thanks, Michal
Hello Michel,
sorry for late reply...
Am 21.01.21 um 09:09 schrieb Michal Simek:
On 1/21/21 5:11 AM, Simon Glass wrote:
Hi Michal,
On Wed, 20 Jan 2021 at 08:50, Michal Simek michal.simek@xilinx.com wrote:
On 1/20/21 4:44 PM, Simon Glass wrote:
Hi Michal,
On Wed, 20 Jan 2021 at 00:46, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 1/19/21 7:54 PM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers
I can't see any issue with it on zynqmp platform. There is only issue with i2c which was there for quite a long time that i2c mux is considered as chip on the subbus as is visible below.
Do you mean the naming of the device, or something else? What happens if you type 'i2c bus'?
If look at log below. mux is at address 74 which is i2c_mux_bus_drv and when you run i2c dev <any i2c mux channel> and run i2c probe i2c mux itself is assigned to to i2c_generic_chip_drv. Below you see it multiple times as generic_74 with ID 2/8/12/14/20. All of them are just targeting i2c mux.
That's strange. I wonder if it is failing to find it and creating multiple copies?
+Heiko Schocher too
I have never had a time to dig into this. But I expect that i2c mux enables one channel and i2c probe just correct detects all devices on bus before mux and also the whole subbus. But we are missing to check for every detected device if that address is listed already.
Me too, I have currently a heavy workload and no time to look into this issue, but it is noted on my list... and my speculation goes into the same direction.
bye, Heiko
Hi Simon,
On Tue, Jan 19, 2021 at 8:54 PM Simon Glass sjg@chromium.org wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://u-boot.readthedocs.io/
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
Regards, Simon
Could you please send me an invitation for the recurring meetings. Thanks
On 1/20/21 11:08 AM, Igor Opaniuk wrote:
Hi Simon,
On Tue, Jan 19, 2021 at 8:54 PM Simon Glass sjg@chromium.org wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://u-boot.readthedocs.io/
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
Regards, Simon
Could you please send me an invitation for the recurring meetings.
for me too please.
Thanks, Michal
Dear All,
On 1/20/21 11:08 AM, Igor Opaniuk wrote:
Hi Simon,
On Tue, Jan 19, 2021 at 8:54 PM Simon Glass sjg@chromium.org wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any
good for East Asia
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://u-boot.readthedocs.io/
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a...
Regards, Simon
Could you please send me an invitation for the recurring meetings.
for me too please.
+1
Thanks, Michal
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
Hi,
On 1/20/21 3:54 AM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
In South Korea, it will be almost am 01:30. Frankly, i can't speak English very well..If it doesn't matter, i hope to attend sometime. :)
Best Regards, Jaehoon Chung
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://protect2.fireeye.com/v1/url?k=93d7f10b-cc4cc86e-93d67a44-000babff32e...
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://protect2.fireeye.com/v1/url?k=030f1752-5c942e37-030e9c1d-000babff32e...
Regards, Simon
On 1/20/21 6:18 PM, Jaehoon Chung wrote:
Hi,
On 1/20/21 3:54 AM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
In South Korea, it will be almost am 01:30. Frankly, i can't speak English very well..If it doesn't matter, i hope to attend sometime. :)\
One option could be to alternate times. E.g. one meeting pick a time best for one hemisphere, and another call pick a time best for the other. For example, the next meeting could be at 4:30 UTC (since we just met at 16:30 UTC)
--Sean
Best Regards, Jaehoon Chung
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://protect2.fireeye.com/v1/url?k=93d7f10b-cc4cc86e-93d67a44-000babff32e...
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://protect2.fireeye.com/v1/url?k=030f1752-5c942e37-030e9c1d-000babff32e...
Regards, Simon
Hi Sean & Jaehoon,
On Wed, 20 Jan 2021 at 16:25, Sean Anderson seanga2@gmail.com wrote:
On 1/20/21 6:18 PM, Jaehoon Chung wrote:
Hi,
On 1/20/21 3:54 AM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
In South Korea, it will be almost am 01:30. Frankly, i can't speak English very well..If it doesn't matter, i hope to attend sometime. :)\
One option could be to alternate times. E.g. one meeting pick a time best for one hemisphere, and another call pick a time best for the other. For example, the next meeting could be at 4:30 UTC (since we just met at 16:30 UTC)
--Sean
Yes I think that is the best option. I'll figure this out.
Re speaking English, U-Boot is a global project so we have to accommodate different people. We have live notes during the meeting so if it is easier you can type things into the notes. Sometimes I find that helps to get points across.
Regards, Simon
Best Regards, Jaehoon Chung
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://protect2.fireeye.com/v1/url?k=93d7f10b-cc4cc86e-93d67a44-000babff32e...
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://protect2.fireeye.com/v1/url?k=030f1752-5c942e37-030e9c1d-000babff32e...
Regards, Simon
Hi,
On 1/21/21 12:26 PM, Simon Glass wrote:
Hi Sean & Jaehoon,
On Wed, 20 Jan 2021 at 16:25, Sean Anderson seanga2@gmail.com wrote:
On 1/20/21 6:18 PM, Jaehoon Chung wrote:
Hi,
On 1/20/21 3:54 AM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
In South Korea, it will be almost am 01:30. Frankly, i can't speak English very well..If it doesn't matter, i hope to attend sometime. :)\
One option could be to alternate times. E.g. one meeting pick a time best for one hemisphere, and another call pick a time best for the other. For example, the next meeting could be at 4:30 UTC (since we just met at 16:30 UTC)
--Sean
Yes I think that is the best option. I'll figure this out.
Re speaking English, U-Boot is a global project so we have to accommodate different people. We have live notes during the meeting so if it is easier you can type things into the notes. Sometimes I find that helps to get points across.
It's helpful to me. :) Thaks!
Best Regards, Jaehoon Chung
Regards, Simon
Best Regards, Jaehoon Chung
- Simon might send out survey
- Send invitation to maintainer group - DONE
[Simon] New sequence numbers [Heinrich] Online docs
- https://protect2.fireeye.com/v1/url?k=93d7f10b-cc4cc86e-93d67a44-000babff32e...
- Accept a merge request only with docs included?
Next meeting Tuesday 2 Feb.
[1] https://protect2.fireeye.com/v1/url?k=030f1752-5c942e37-030e9c1d-000babff32e...
Regards, Simon
Hi,
On 1/21/21 5:09 AM, Jaehoon Chung wrote:
Hi,
On 1/21/21 12:26 PM, Simon Glass wrote:
Hi Sean & Jaehoon,
On Wed, 20 Jan 2021 at 16:25, Sean Anderson seanga2@gmail.com wrote:
On 1/20/21 6:18 PM, Jaehoon Chung wrote:
Hi,
On 1/20/21 3:54 AM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
In South Korea, it will be almost am 01:30. Frankly, i can't speak English very well..If it doesn't matter, i hope to attend sometime. :)\
One option could be to alternate times. E.g. one meeting pick a time best for one hemisphere, and another call pick a time best for the other. For example, the next meeting could be at 4:30 UTC (since we just met at 16:30 UTC)
--Sean
Yes I think that is the best option. I'll figure this out.
Re speaking English, U-Boot is a global project so we have to accommodate different people. We have live notes during the meeting so if it is easier you can type things into the notes. Sometimes I find that helps to get points across.
It's helpful to me. :) Thaks!
Definitely language can be a barrier but if there is option to write via chats, docs it should be fine. Everybody understands that it can be hard to understand but this is open community that you can answer by yes/no. And it is not shame to ask to repeat stuff again because of language barrier or unstable internet connection. I believe that it is also difficult to learn your language for other.
Cheers, Michal
On 1/21/21 5:05 PM, Michal Simek wrote:
Hi,
On 1/21/21 5:09 AM, Jaehoon Chung wrote:
Hi,
On 1/21/21 12:26 PM, Simon Glass wrote:
Hi Sean & Jaehoon,
On Wed, 20 Jan 2021 at 16:25, Sean Anderson seanga2@gmail.com wrote:
On 1/20/21 6:18 PM, Jaehoon Chung wrote:
Hi,
On 1/20/21 3:54 AM, Simon Glass wrote:
Hi,
Thank you for attending!
Full notes at [1]
Tuesday 19 January 2021
Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean Anderson, Simon Glass, Walter Lozano
Notes: [all] Introductions [all] Timing of call
- Current time is the best across US, Europe, India. But not any good
for East Asia
In South Korea, it will be almost am 01:30. Frankly, i can't speak English very well..If it doesn't matter, i hope to attend sometime. :)\
One option could be to alternate times. E.g. one meeting pick a time best for one hemisphere, and another call pick a time best for the other. For example, the next meeting could be at 4:30 UTC (since we just met at 16:30 UTC)
--Sean
Yes I think that is the best option. I'll figure this out.
Re speaking English, U-Boot is a global project so we have to accommodate different people. We have live notes during the meeting so if it is easier you can type things into the notes. Sometimes I find that helps to get points across.
It's helpful to me. :) Thaks!
Definitely language can be a barrier but if there is option to write via chats, docs it should be fine. Everybody understands that it can be hard to understand but this is open community that you can answer by yes/no. And it is not shame to ask to repeat stuff again because of language barrier or unstable internet connection. I believe that it is also difficult to learn your language for other.
Sure, i didn't never think about using my language on community. :)
Best Regards, Jaehoon Chung
Cheers, Michal
participants (12)
-
Alex Sadovsky -
Bin Meng -
Heiko Schocher -
Heinrich Schuchardt -
Igor Opaniuk -
Jaehoon Chung -
Lukasz Majewski -
Marek Vasut -
Michal Simek -
Sean Anderson -
Simon Glass -
Stefano Babic