Skip to content

Update README with virtio config and bridge setup instructions#90

Closed
CharleneChar wants to merge 2 commits intosysprog21:mainfrom
CharleneChar:main
Closed

Update README with virtio config and bridge setup instructions#90
CharleneChar wants to merge 2 commits intosysprog21:mainfrom
CharleneChar:main

Conversation

@CharleneChar
Copy link
Copy Markdown
Contributor

Add instructions to disable the virtio network driver so the virtio device can bind to the vwifi driver. Document the expected CONFIG setting in .config and provide menuconfig navigation steps.

Also include steps to bring up the bridge device (br0) required for networking setup.

Add instructions to disable the virtio network driver so the virtio
device can bind to the vwifi driver. Document the expected CONFIG
setting in .config and provide menuconfig navigation steps.

Also include steps to bring up the bridge device (br0) required
for networking setup.
$ sudo ip link set tap2 master br0
```

Start `bridge` device:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Avoid necessary backticks.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing this out. I’ve created PR #92 to address this issue, and I’ll follow up and resolve it in that PR.

$ make menuconfig
```
The default kernel configuration will work for our testing environment, so just click `save` and we get `.config` on the top directory.
To allow virtio device to be bound to vwifi driver, please ensure the virtio network driver is disabled before you click `save`. By excluding the virtio network driver, you should spot `CONFIG_VIRTIO_NET=n` in the `.config` file on the top directory.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Explain the rationale.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing this out. I’ve created PR #92 to address this issue, and I’ll follow up and resolve it in that PR.

Add conditional compilation for kernel >= 6.17 to handle the
updated cfg80211 tx power callbacks, which introduce the
radio_idx parameter in set_tx_power() and get_tx_power().

Also preserve compatibility with earlier kernels by keeping
existing signatures under appropriate LINUX_VERSION_CODE checks,
including link_id handling introduced in 6.14.

This fixes autobuild failures on newer kernel versions
without affecting older versions.
Copy link
Copy Markdown
Contributor

@jserv jserv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Split code changes and documentation refinements into two pull requests.

@CharleneChar
Copy link
Copy Markdown
Contributor Author

Split code changes and documentation refinements into two pull requests.

Thanks for the review.

I’ve split the changes into two separate PRs for clarity and easier review:

I’ll close this PR and continue the discussion in those threads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants